Preventing an atomic copy
Andrew Hamer-Adams
andrew at factorial.co.nz
Mon Feb 2 19:30:25 MST 2015
We require an option that forces rsync to truncate the destination file to zero bytes, using the existing inode, before copying (non-atomic).
For various important reasons, we cannot use —inplace as an option due to the way the filesystem we use handles a retrieve from tape.
Using —temp-dir as an option does provide us with the functionality we require, however it has obvious downsides of doubling I/O for no good reason.
Am I missing something obvious? Or should I add this as a feature request?
Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/rsync/attachments/20150203/43e532e9/attachment.html>
More information about the rsync
mailing list