Rsync --timeout argument ignores non-transfer progress
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rsync (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I want rsync to timeout if it is unable to continue making progress on a remote backup over ssh.
For example, if the remote destination server is rebooted, I don't want this to cause an orphaned process on the source computer.
However, if I use the "--timeout" argument (--timeout=180), it will timeout prematurely while evaluating large files, during which, progress is indeed being made, but since no data is actually being transfered (for period longer that 180 secounds), it make rsync exit (even though it is really progressing).
This has been discussed before:
https:/
Either the timeout argument needs to be changed to take this type of progress into consideration, or another argument should be added to rsync that DOES indeed take this type of progress into consideration before invoking a timeout.
This would need to be implemented upstream and the link you provided does not sound like that will happen.
Ubuntu will only get this if upstream implements it.