The manual says that a file being transfered is removed if rsync gets an interruption and --partial is not used or implied by other options like partial-dir or delay-updates. However I've found that a file was left after interruption, with a zero size. Would it be possible that rsync doesn't delete the partial file if it's not yet written to it? This is 3.0.6 on linux. Both processes were killed with the same command, kill pid1 pid2.
On Fri, Jul 03, 2009 at 03:32:29PM -0300, Carlos Carvalho wrote:> Both processes were killed with the same command, kill pid1 pid2.A SIGTERM (the default kill signal) should be caught by rsync, allowing it to cleanup before it exits.> However I've found that a file was left after interruption, with a > zero size.What kind of file? A temp file, or the destination file? You didn't use --inplace, right? Rsync 2.6.8 had a bug where it could leave a temp file when interrupted, but I don't see any such problem with 3.0.6. ..wayne..
Apparently Analagous Threads
- [nbdkit PATCH] tests: Swap nbdkit process order in test-nbd-tls-psk.sh
- [nbdkit PATCH v2 5/5] nbd: Test .extents
- [PATCH nbdkit] tests: Cancel trap in cleanup function to avoid recursive traps.
- [nbdkit PATCH 3/3] nbd: Implement .list_exports
- [PATCH v2 nbdkit 4/5] tests: Use a generic cleanup mechanism instead of explicit trap.