DO NOT REPLY [Bug 3304] on --delay-updates remove .~tmp~ recursively
bugzilla-daemon at dp3.samba.org
bugzilla-daemon at dp3.samba.org
Tue Jan 17 19:38:08 GMT 2006
https://bugzilla.samba.org/show_bug.cgi?id=3304
wayned at samba.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Comment #2 from wayned at samba.org 2006-01-17 12:38 MST -------
It might not be safe for rsync to delete a non-empty .~tmp~ dir if multiple
rsync commands are running at the same time (hopefully updating different
files). One could argue that two simultaneously running rsyncs should really
be using different partial-dir settings to avoid other potential failures (such
as an empty directory being removed by one rsync right before the other can
open a temp file in it). I'll consider allowing this, but it might be better
to make this an option, or to only enable it if a custom --partial-dir name is
chosen.
As for your example, rsync does not remove the empty .~tmp~ dir because it
didn't use it during that run. If rsync had updated a file in the destination
directory, it would have removed the dir (as long as it was empty). This
behavior is certainly debatable, and might change in the future.
--
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.
More information about the rsync
mailing list