Mention the change in how "incoming chmod" works when --perms was

not specified.

Mention the change in how "incoming chmod" works when --perms was
not specified.
44a8e86d · Wayne Davison · 73abdda4 · 44a8e86d
Commit 44a8e86d authored Feb 19, 2006 by Wayne Davison
Hide whitespace changes
Inline Side-by-side

Showing with 3 additions and 4 deletions

rsyncd.conf.yo rsyncd.conf.yo +3 -4

No files found.
--- a/rsyncd.conf.yo
+++ b/rsyncd.conf.yo
@@ -266,10 +266,9 @@ See the "exclude" option above.
 dit(bf(incoming chmod)) This option allows you to specify a set of
 comma-separated chmod strings that will affect the permissions of all
 incoming files (files that are being received by the daemon).  These
-changes happen after any user-requested changes the client requested via
+changes happen after all other permission calculations, and this will
-bf(--chmod).  Note, however, the if the client didn't specify bf(--perms),
+even override destination-default and/or existing permissions when the
-the daemon's umask setting will still mask the value before it is used, so
+client does not specify bf(--perms).
-be sure it is set appropriately if this is a concern.
 See the description of the bf(--chmod) rsync option and the bf(chmod)(1)
 manpage for information on the format of this string.