creativeprojects
Lock settings do not apply to interactive sessions
It seems that any locking settings, such as timeouts and retries (schedule-lock-* and restic-lock controls in [global]), only apply to scheduled jobs, or this is the result of what I came up with after debugging my locking setup for 2h and it seemingly not working -- until I actually triggered the systemd backup services instead of running resticprofile manually. Is this intentional?
Indeed all the schedule-* flags only apply when the job is started from a schedule.
For the global flags, you need to add the --lock-wait flag on the command line, as documented here.
When running directly on the command line, it's usually preferable to get an instant fail from a lock since you're behind the console to inspect and remove the lock manually.
Can we document this better, then? I did not find this from the documentation.