ea59896bd6
Fixes restic#719 If the option is passed, restic will wait the specified duration of time and retry locking the repo every 10 seconds (or more often if the total timeout is relatively small). - Play nice with json output - Reduce wait time in lock tests - Rework timeout last attempt - Reduce test wait time to 0.1s - Use exponential back off for the retry lock - Don't pass gopts to lockRepo functions - Use global variable for retry sleep setup - Exit retry lock on cancel - Better wording for flag help - Reorder debug statement - Refactor tests - Lower max sleep time to 1m - Test that we cancel/timeout in time - Use non blocking sleep function - Refactor into minDuration func Co-authored-by: Julian Brost <julian@0x4a42.net>
8 lines
303 B
Text
8 lines
303 B
Text
Enhancement: Add --retry-lock option
|
|
|
|
This option allows to specify a duration for which restic will wait if there
|
|
already exists a conflicting lock within the repository.
|
|
|
|
https://github.com/restic/restic/issues/719
|
|
https://github.com/restic/restic/pull/2214
|
|
https://github.com/restic/restic/pull/4107
|