Re: [External] Re: ctrl -c while executing --progress --size-only --partial results in unhidden but incomplete file

Rsync has no memory of what other instances of rsync have done in the past. An existing file with a different name is of no interest to it unless --delete in which case it would be deleted. Maybe what you really want is --partial-dir? On 6/7/23 16:17, Lacey, Nathan wrote: I'm suggesting a p

Re: [External] Re: ctrl -c while executing --progress --size-only --partial results in unhidden but incomplete file

I'm suggesting a partial file that isn't hidden is worse. Because any other app looking at the file would think the transfer is complete and try to use it. It doesn't need to be a orphaned file, when called next time with --partial rsync could re-opened the incomplete/hidden file, than it could

Re: ctrl -c while executing --progress --size-only --partial results in unhidden but incomplete file

That is what --partial does. It keeps the partial file. If it kept the temporary file with the random file name that would just be a useless orphaned file. On 6/7/23 15:02, Lacey, Nathan via rsync wrote: This is a clone from https://github.com/WayneD/rsync/issues/484

ctrl -c while executing --progress --size-only --partial results in unhidden but incomplete file

This is a clone from https://github.com/WayneD/rsync/issues/484 run rsync with --progress --size-only --partial (version 3.1.2) also tested/built current master ( 3.3.0pre1-5-g6f3c5ecc ) everything works fine unless I interrupt a transfer ( ctrl c ) I would expect to see the incomplete, temporar