From 44a8e86d471cdf0a2b5d4523b8dcc3a9774df17e Mon Sep 17 00:00:00 2001 From: Wayne Davison Date: Sun, 19 Feb 2006 23:58:59 +0000 Subject: [PATCH] Mention the change in how "incoming chmod" works when --perms was not specified. --- rsyncd.conf.yo | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/rsyncd.conf.yo b/rsyncd.conf.yo index 7be14004..2415804c 100644 --- 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 -bf(--chmod). Note, however, the if the client didn't specify bf(--perms), -the daemon's umask setting will still mask the value before it is used, so -be sure it is set appropriately if this is a concern. +changes happen after all other permission calculations, and this will +even override destination-default and/or existing permissions when the +client does not specify bf(--perms). See the description of the bf(--chmod) rsync option and the bf(chmod)(1) manpage for information on the format of this string. -- 2.34.1