tu...@posteo.de wrote: > > ...I just wanted to check, whether there is water in the pool... :) > > I minute ago I found this: > https://unix.stackexchange.com/questions/203018/interrupting-rsync-with-ctrl-c-should-i-use-partial-or-append > > which rises a question about how to resume an interrypted > rsync-session. > It looks like the final answer was not found... > > Any additional ideas about that? > Cheers! > Meino >
I have interrupted rsync quite a few times and never had it fail on resume. I've tested it to be sure. I always use the -v and --progress options so I can watch what it is doing. If I restart it, it picks up right where it left off, if no other files have changed since I stopped it. On occasion Seamonkey or Firefox will write to a file and it catches those too but it updates the file it was stopped on and either completes it or updates it one. I don't know about the technical answer but that's my experience with it. Another thing, if you do have to stop it and feel the need, rerun it with a complete run afterwords to let it double check. If nothing changes, you should be fine. Using du to check data sizes may help to, although sometimes different file systems can change those. Just a couple thoughts. Dale :-) :-)
