DO NOT REPLY [Bug 4128] Make --ignore-times work better with --link-dest by adding an after-transfer check

samba-bugs at samba.org samba-bugs at samba.org
Sat Sep 30 15:34:15 GMT 2006


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


wayned at samba.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
             Status|NEW                         |ASSIGNED
            Summary|ignore-times with link-dest |Make --ignore-times work
                   |behaves unexpected /        |better with --link-dest by
                   |sematics not clear          |adding an after-transfer
                   |                            |check




------- Comment #2 from wayned at samba.org  2006-09-30 10:34 MST -------
The --link-dest option only links files together that are found to be identical
during the pre-transfer identicality checking, never as an extra check after a
file has been updated (though it would be nice to add that as an improvement at
some point, it doesn't work that way at present).

So, I think the new behavior in CVS is misguided in its attempt to make the
--link-dest option play nice with the --ignore-times option.  I've removed that
code and also added a mention to the --link-dest section that --ignore-times
will prevent any hard-linking from occurring (though it will use the hierarchy
to make the transfers more efficient).

I'll turn this bug report into a feature request:

It would be nice if the receiver would notice that it copied 100% of the data
from a --link-dest basis file to the destination temp file while also having
all preserved attributes the same.  Such a file would get its temp file dropped
and the destination file hard-linked to the --link-dest basis file.


-- 
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.


More information about the rsync mailing list