rsync - May 2008 - DO NOT REPLY [Bug 5442] New: setting times to symlinks which do not point to existing files causes error reports

https://bugzilla.samba.org/show_bug.cgi?id=5442

           Summary: setting times to symlinks which do not point to existing
                    files causes error reports
           Product: rsync
           Version: 3.0.3
          Platform: All
        OS/Version: Mac OS X
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned@samba.org
        ReportedBy: ij.list@gmail.com
         QAContact: rsync-qa@samba.org


When changing times on a symlink in Mac OS X, the system actually sets the
times on the symlink destination file. If the destination file does not exist,
syscall returns error.

This behaviour causes rsync to report many "failed to set times on"
errors when
source/destination directories contain symlinks which do not point to existing
files. It would be nice if (on Mac OS X only) setting of times to symlinks
would be appropriately guarded or not executed at all since it does not behave
correctly.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=5442


wayned@samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME




------- Comment #1 from wayned@samba.org  2008-05-06 09:52 CST -------
Rsync only tries to set times on symlinks if the lutimes() function exists.  On
my version of OS X (Panther) the setting of the time on a symlink worked fine. 
If your system says it has lutimes() but it doesn't work, comment out the
HAVE_LUTIMES in config.h and recompile.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.