Intention of unlocking the repository (should this only check exclusive locks?)

[juanboro]

Hi -
As I understand the current releases of restic --- locking in restic is either 'exclusive' or not. Exclusive locks are just for restic operations like forget, prune, and clean (maintenance in this script). Is the intention of the current code checking locks and removing them intended for just the exclusive maintenance locks or all locks?

There are currently two PRs I see related to this:
#120 - Which adds a config switch that makes the lock checking and removal optional (PR also adds a separate time parameter feature)
#135 - Which adds an option to skip the backup/maintenance and try again after some delay if any locks are present.

My take on what this should do given how restic works (currently on a feature on my own feature branch):

• Since non-exclusive locks should not be an issue for backup operations - for the backup operation - only check for existence of exclusive locks (and apply the logic around Add $AutoUnlock toggle to handle repository collisions #135 as needed if they exist).
• For maintenance operation - use the logic from Add $AutoUnlock toggle to handle repository collisions #135 (there should be no locks present to start maintenance operation)

My setup currently sets $AutoUnlock=false and SnapshotMaintenanceEnabled=$false --- since I am running with multiple hosts backing up to the same repository and do the maintenance operations later outside of this.

Before I add another similar(but different/conflicting) PR related to the two above -- I want to see if I'm misunderstanding something.