I wrote a patch for rsync 2.6.6 that changes two things: (1) When the receiving rsync creates a file in a directory with a default ACL and `--perms' is off, rsync uses the default ACL instead of the umask to calculate the new file's permissions. All programs that just use `open' and don't do an explicit `chmod' are forward-compatible with default ACLs, but rsync always sets permissions itself, so it had to be modified to handle default ACLs correctly. (2) Even if `--perms' is off, rsync preserves executability of files. The precise semantics are explained in the patched man page. The patch is attached. If you're interested in these features, please test it and tell me if you have any problems with it. I request that the patch be included in the `patches' directory of the next release of rsync if it is found to work correctly. -- Matt McCutchen, ``hashproduct'' hashproduct@verizon.net -- mysite.verizon.net/hashproduct -------------- next part -------------- A non-text attachment was scrubbed... Name: better-perms.diff Type: text/x-patch Size: 11718 bytes Desc: not available Url : lists.samba.org/archive/rsync/attachments/20050903/6498b3e0/better-perms.bin
A while ago, I wrote to the list:> I wrote a patch for rsync 2.6.6 that changes two things: [default ACLs > and preserving executability]In case it matters to anyone: I've been using the patched rsync (actually, I made additional changes after that patch) and it works decently...but I've convinced myself that any attempt to get rsync to observe default permissions cleanly and correctly in all cases is doomed to failure due to the many "chmod" calls it uses. Oh well. Perhaps the fancy pluggable tar/rsync program, if it is ever written, could do better. -- Matt McCutchen, ``hashproduct'' hashproduct@verizon.net -- mysite.verizon.net/hashproduct