Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Nov 2008 01:01:45 -0800 (PST)
From:      Nate Eldredge <neldredge@math.ucsd.edu>
To:        Volodymyr Kostyrko <c.kworr@gmail.com>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: Unprivileged user can't set sticky bit on a file; why?
Message-ID:  <Pine.GSO.4.64.0811140100510.1597@zeno.ucsd.edu>
In-Reply-To: <gfjdqe$9kv$1@ger.gmane.org>
References:  <Pine.GSO.4.64.0811132245120.1597@zeno.ucsd.edu> <gfjdqe$9kv$1@ger.gmane.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Nov 2008, Volodymyr Kostyrko wrote:

> Nate Eldredge wrote:
>
>> I came across this when trying to rsync some files which had the sticky bit 
>> set on the remote side.  (It's the historical Unix archive from tuhs.org; 
>> the files in question are part of an unpacked V7 UNIX installation, for 
>> which the sticky bit of course had meaning. :-) )  It's annoying that this 
>> makes rsync fail; it messes up my mirroring script.
>
> You can ask rsync to change file attributes on the fly with the --chmod 
> option. Just my 2c.

Thanks for this hint.  "--chmod=F-t" solves my problem.  But I am still 
curious about this behavior.

-- 

Nate Eldredge
neldredge@math.ucsd.edu



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0811140100510.1597>