> Note that back-to-back rsyncs make the window of opportunity much > much smaller for things to change during transit.
yes, but it still leaves room for corrupted transfers nobody would probably know about !? > -----Ursprüngliche Nachricht----- > Von: <[EMAIL PROTECTED]> > Gesendet: 16.09.07 18:24:23 > An: "'roland'" <[EMAIL PROTECTED]> > CC: <rsync@lists.samba.org> > Betreff: RE: File changed during save.... > > Matt McCutchen wrote: > > > > On 9/15/07, roland <[EMAIL PROTECTED]> wrote: > > > what`s the rsync equivalent to this? > > > how can i see which files changed while rsync was > > transferring them ? > > > > Handling of concurrent changes to source files is one of rsync's > > weaknesses. The rsync sender naively reads each source file from > > beginning to end and sends what it sees; it doesn't detect if source > > files change while being transferred. In many cases, the concurrent > > modification will leave the source file with an mtime different from > > the mtime rsync saw when it statted the file during file-list building > > (which gets set on the destination file), so a subsequent rsync run > > will fix the corrupted destination file. See this thread for more > > information: > > > > http://lists.samba.org/archive/rsync/2006-January/014534.html > > > > Matt > > -- > > Note that back-to-back rsyncs make the window of opportunity much > much smaller for things to change during transit. > > ______________________________________________________________________ XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club! Jetzt testen! http://produkte.web.de/club/?mc=021130 -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
