Possible exclude bug in 2.5.5 in rsyncd.conf

Dave Dykstra dwd at bell-labs.com
Mon May 13 08:42:02 EST 2002

On Fri, May 10, 2002 at 05:19:47PM -0400, pyxl wrote:
> Hello all,
> I've found some behavior in 2.5.5 that is contrary to the documentation 
> in the man page.
> Specifically, I'm running an rsync server (i.e. from inetd with 
> --daemon),and in the module definition I'm specifying the line "exclude 
> nosyncdir".  The documentation for rsyncd.conf indicates that this is 
> exactly equivalent to using "--exclude nosyncdir" on the client side. 
> I'm finding, however, that if I specify it on the server side, it's 
> ignored, and the dir structure of nosyncdir and below is transferred. 
> If I use the client side option however, it works as expected, that 
> being the nosyncdir dir structure is not transferred.
> I've tried the variations *nosyncdir*, *nosyncdir/*, nosyncdir, 
> nosyncdir/* and nosyncdir* - none of them work on the server side.
> Hopefully someone can shine some light on this, either to confirm that 
> it's a bug or correct my syntax if it's off.

Do you happen to be sending to the daemon?  It only works for receiving
files from a daemon.  Last week I changed the rsyncd.conf man page as

    This is equivalent to the client specifying these patterns with the
    --exclude option, except that the exclude list is not passed to the
    client and thus only applies on the server and also only applies when
    receiving files from a server and not when sending files to it.

- Dave Dykstra

More information about the rsync mailing list