The prune hangs only after a backup was killed mid-run; the lock file stays behind.
The prune hangs only after a backup was killed mid-run; the lock file stays behind.
Should the unlock run before every prune, or only when the lock is older than the last backup?
Only when it is stale: a live backup holds a fresh lock.
Done in prune.go: the lock's age is checked against the last snapshot.
The outcome line should name the PID that holds the lock.
It does now: repository is locked by PID 4120.