rsync 2.5.5 and the exclude directive - additional behavior

[Dave Dykstra]

On Mon, May 13, 2002 at 10:06:18AM -0400, pyxl wrote:
> And, I've found more.
> 
> It turns out that even though the exclude directive is ignored for 
> inbound data in rsyncd.conf, it is NOT ignored for the --delete option. 
> I've seen this behavior occur when I've deleted a file from the sending 
> side (client) that is inside a tree that's matched by the server-side 
> (rsyncd) exclude directive.  The deletion is ignored, as the 
> documenation indicates that it should be.


I'm submitting the following change to the docs:

--- /tmp/rsyncd.conf.yo Mon May 13 12:52:15 2002
+++ rsyncd.conf.yo      Mon May 13 13:12:43 2002
@@ -176,8 +176,11 @@
 separated list of patterns to add to the exclude list. 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.  Only one "exclude" option may be specified, but
+the server: that is, it excludes files received by a client when receiving
+from a server and files deleted on a server when sending to a server, but
+it doesn't exclude files sent from a client when sending to a server or
+files deleted on a client when receiving from a server.  
+Only one "exclude" option may be specified, but
 you can use "-" and "+" before patterns to specify exclude/include.
 
 Note that this option is not designed with strong security in


- Dave Dykstra