You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support lock-wait with --lock-retry in restic 0.16 (#240)
* Support lock-wait with --lock-retry in restic 0.16
* Simplified logic and relaxed min stale-lock age
* Supporting custom overridden "lock-retry" values
* Improved logging and aligned documentation
Copy file name to clipboardExpand all lines: config/global.go
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ type Global struct {
19
19
ResticVersionstring// not configurable at the moment. To be set after ResticBinary is known.
20
20
FilterResticFlagsbool`mapstructure:"restic-arguments-filter" default:"true" description:"Remove unknown flags instead of passing all configured flags to restic"`
21
21
ResticLockRetryAfter time.Duration`mapstructure:"restic-lock-retry-after" default:"1m" description:"Time to wait before trying to get a lock on a restic repositoey - see https://creativeprojects.github.io/resticprofile/usage/locks/"`
22
-
ResticStaleLockAge time.Duration`mapstructure:"restic-stale-lock-age" default:"2h" description:"The age an unused lock on a restic repository must have at least before resiticprofile attempts to unlock - see https://creativeprojects.github.io/resticprofile/usage/locks/"`
22
+
ResticStaleLockAge time.Duration`mapstructure:"restic-stale-lock-age" default:"1h" description:"The age an unused lock on a restic repository must have at least before resiticprofile attempts to unlock - see https://creativeprojects.github.io/resticprofile/usage/locks/"`
23
23
ShellBinary []string`mapstructure:"shell" default:"auto" examples:"sh;bash;pwsh;powershell;cmd" description:"The shell that is used to run commands (default is OS specific)"`
24
24
MinMemoryuint64`mapstructure:"min-memory" default:"100" description:"Minimum available memory (in MB) required to run any commands - see https://creativeprojects.github.io/resticprofile/usage/memory/"`
25
25
Schedulerstring`mapstructure:"scheduler" description:"Leave blank for the default scheduler or use \"crond\" to select cron on supported operating systems"`
Copy file name to clipboardExpand all lines: docs/content/usage/locks/index.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -121,7 +121,7 @@ In some cases, resticprofile as well as restic may leave a lock behind if the pr
121
121
122
122
For that matter, if you add the flag `force-inactive-lock` to your profile, resticprofile will detect and remove stale locks:
123
123
***resticprofile locks**: Check for the presence of a process with the PID indicated in the lockfile. If it can't find any, it will try to delete the lock and continue the operation (locking again, running profile and so on...)
124
-
***restic locks**: Evaluate if a restic command failed on acquiring a lock. If the lock is older than `restic-stale-lock-age`, invoke `restic unlock` and retry the command that failed (can be disabled by setting `restic-stale-lock-age` to 0, default is 2h).
124
+
***restic locks**: Evaluate if a restic command failed on acquiring a lock. If the lock is older than `restic-stale-lock-age`, invoke `restic unlock` and retry the command that failed (can be disabled by setting `restic-stale-lock-age` to 0, default is 1h).
0 commit comments