>http://olstrans.sourceforge.net/release/OLS2000-rsync/OLS2000-rsync.html
<snipp>
But the filename twice can happen under other circumstances; if you've seen this happen, it's almost certainly because the file changed during transfer. Rsync does no locking. Which means that: if you are modifying a file while it's being transferred, then probably the checksum will fail and it'll go round again. And if it goes around twice, and it still fails, then it prints a message saying; Error, checksum failed, file changed during transfer? And it's probably a file like a log file that's being constantly updated and so the checksums didn't match because it's never going to be able to get it exact; it means that what you've got on the other end is something which will approximate some snapshot of the file, but because it's not doing any locking, it can't guarantee that it's got a particular snapshot of the file, because you can't have an atomic read of the whole file. [31m, 49s]
<snipp>
receiving incremental file list
test/test.dat
total size is 329252864 speedup is 3.97
Von: devz...@web.de
An: rsync@lists.samba.org
Betreff: rsync show files changed during transfer - how?
apparently, rsync can't show that information?
wouldn't that be an extremely useful feature if rsync could do another additional mtime or even checksum comparison after each file transfer?
for example emc networker notifies about "changed during save". i'm curious wg rsync doesn't
regards
roland
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.-- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
-- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html