https://bugzilla.samba.org/show_bug.cgi?id=1479
Summary: --compare-dest suppresses output file if same timestamp
present
Product: rsync
Version: 2.5.7
Platform: All
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P3
Component: core
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
QAContact: [EMAIL PROTECTED]
If I try to rsync a file that has an exact size & timestamp match in my
--compare-dest directory, then the file is not created in the output directory.
This behavior is as documented, but it is inconvenient for my application: I
repeatedly rsync a directory of files from a slow server, and I want to use
another directory as a cache on the destination machine without influencing the
correctness of the transfer. I don't want to use --link-dest because it changes
the semantics; it's too easy to mangle a file when it's hard linked. I am
working around the problem by messing up the timestamps of everything in my
compare-dest directory. I think this means that it can use the compare-dest as a
hash matching source, but will still create the output file in all cases.
So this bug is a feature request for a --copy-dest or
--create-the-output-file-anyway-please option. Or maybe it's just my way of
asking if I'm being an idiot.
--
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.
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
