rsync and BSD file flags.

Jonathan Call jcall at
Tue Mar 28 19:01:51 GMT 2006

Just an update for you:
I did not have autoconf on my test box, so I just stuck HAVE_CHFLAGS
into config.h. It appears to work. Rsync seems to immediately recognize
the schg flag on files on the local system and then won't write the file
from the remote side. ;)

Running it once without the --flags option and then running it with the
--flags option seems to be a workaround in that respect.


> -----Original Message-----
> From: Wayne Davison [mailto:wayned at]
> Sent: Tuesday, March 21, 2006 3:08 PM
> To: Jonathan Call
> Cc: rsync at
> Subject: Re: rsync and BSD file flags.
> On Tue, Mar 21, 2006 at 03:59:45PM -0500, Jonathan Call wrote:
> > rsync: file flags are not supported on this client.
> This means that the source was patched (since that message is not
> without the patch) but that it was not configured with chflags
> Did you run ./prepare_source after applying the patch?  Without that,
> configure would not have been updated (you'll need autoconf for that
> command to work).
> If configure finds the chflags function, it should automatically
> HAVE_CHFLAGS in your config.h.  If not, you could try manually
> the HAVE_CHFLAGS line in config.h to be "#define HAVE_CHFLAGS 1" and
> recompiling (but that shouldn't be necessary).  If you don't have
> autoconf around, you could manually add that line to config.h (the
> command you cited would not have been enough to define this for the
> programs being compiled).
> Also: I noticed a problem with the definition of SUPPORT_FLAGS in the
> first patch:  the define wasn't being set early enough in the file.
> should grab an updated flags.diff patch or manually move the 3 lines
> that conditionally define SUPPORT_FLAGS to a spot earlier in rsync.h
> (prior to the one spot that checks the define in the file).
> ..wayne..

More information about the rsync mailing list