Hi, is there a way to ignore the permissions for symlinks but compare the permissions for regular files and change them accordingly? The problem is that using OS X every time I run rsync it tries to update the permissions for the symlinks but the changes are not made since OS X has no support for symlink permissions. Therefore it would like to somehow ignore symlink permissions. Thanks, Mario
On Oct 13, 2007, at 8:56 PM, dsp@gmx.org wrote:> since OS X has no support for symlink permissionsActually, this isn't quite true. osx has no lchmod, but if you set a umask before creating the link, the permissions are set. So, as opposed to ignoring the permissions, perhaps we should teach rsync how to set them. I'll probably look at this as soon as I'm done writing a patch for preserving the creation date.
On Sat, Oct 13, 2007 at 08:56:23PM +0200, dsp@gmx.org wrote:> is there a way to ignore the permissions for symlinks but compare the > permissions for regular files and change them accordingly?That should be the default for any system that doesn't have lchmod(). ..wayne..
On Tue, Oct 16, 2007 at 12:38:19PM +0200, Wesley W. Terpstra wrote:> Someone with an intel mac should test this to check the uint32_t works > there too (I have a powerpc).It worked fine for a simple test. The latest CVS code now has your lchmod() alternative if setattrlist() is around. Thanks! Now we'll see if any unexpected systems are affected by this change (I'm not expecting any, though). ..wayne..
Possibly Parallel Threads
- lchmod for osx (was: Symlinks in OS X (10.4.1))
- [Bug 2913] New: rsync of symlinks on >=bsd needs lutimes(2) and lchmod(2)
- Prevent dereferenced path of symlinked directories from printing on client side log output
- OS X client symlinks
- Two file mode bugs in puppet 0.25?