rsync - May 2020 - [Bug 14394] New: Add an option for --remove-source-files to remove files right away

https://bugzilla.samba.org/show_bug.cgi?id=14394

            Bug ID: 14394
           Summary: Add an option for --remove-source-files to remove
                    files right away
           Product: rsync
           Version: 3.2.0
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: core
          Assignee: wayne at opencoder.net
          Reporter: gfa at zumbi.com.ar
        QA Contact: rsync-qa at samba.org
  Target Milestone: ---

Hello

I want to have an option to change the behavior of --remove-source-files to
remove the file right after it was transfer instead of after the whole
operation finished.

My use case is to move files between systems with bad connectivity and
low disk space, on the recv side the files are deleted soon after
receiving them making rsync to download them again if the last sync
operation didn't finish correctly.

I use rsync like a queue in this case, sort of


thank you so much for the wonderful rsync!

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=14394

Wayne Davison <wayne at opencoder.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|NEW                         |RESOLVED

--- Comment #1 from Wayne Davison <wayne at opencoder.net> ---
Rsync needs to ensure that the receiver created the file before the sender
removes it or you could have the file vanish when an error occurs (and exist on
neither side).  The deletion delay is somewhat large due to how much data is
pushed down the socket from the generator. You could try specifying the
--whole-file (-W) option to speed it up, but this would mean that any updated
files that exist on both sides would be resent in total with no matching-data
computations. You could also try breaking up the copy operations into single
directories (use -d instead of -r) so that rsync finishes up each (smaller)
operation more rapidly.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.