Matt McCutchen wrote: > 1. Wait for a short time after a change to the source occurs before > propagating it. If a file is created and then rapidly deleted, no > action is necessary. Implementing this fully would require a data > structure to remember pending changes; it would have to be somewhat > sophisticated to handle moves optimally.
> 2. Somehow get rsync to treat disappearance of the source file as "file > has vanished" rather than an error. This could be done inelegantly by > running rsync on the top source directory but excluding everything > except the changed file(s). It might be better to use a modified rsync > with an option that causes it to treat any and all missing source > args/--files-from entries as "file has vanished". > 3. Figure out why continusync is exiting altogether when rsync returns > error 23 and stop it from doing that. Thanks for the fast response, Matt. I think we'll try to do #2 locally as a patch. I'll let you know how it works out. Best regards, Charles
-- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
