samba-bugs@samba.org
2005-Nov-01 17:21 UTC
[Bug 3229] Don't make backup file if destination file wasn't modified
https://bugzilla.samba.org/show_bug.cgi?id=3229 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2005-11-01 10:10 ------- Just to be clear: rsync already avoids files that it didn't transfer. If you aren't preserving timestamps (-t), rsync will update files that haven't really changed (because their modified times differ). You can use the -c (--checksum) option as one (expensive) way to avoid re-sending files that have not changed their data, but do not match in modified time. However, you may be suggesting that rsync be able to check if the updated file that it just created was created a 100% match of the local file's data. In that case, it should be possible to go ahead and skip the backup step (as long as --inplace wasn't specified). We might not even need an option for this (though I'd need to think about the ramifications of that). -- 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.
Seemingly Similar Threads
- [Bug 3229] New: Don't make backup file if destination file wasn't modified
- DO NOT REPLY [Bug 7337] New: sparse files not equally sparse on destination
- DO NOT REPLY [Bug 4834] New: --inplace with --backup --backup-dir does not work
- [Bug 11075] New: Shouldn't --inplace fail immediately if it can't make files?
- [Bug 1646] New: --inplace with --backup --backup-dir does not work