Locks: admin-configurable expiry cap for manual locks (#394) #397
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "lock-cap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements #394 (deferred L4 from #315).
lockMaxHourssetting (0 = off, the default) with validation, persisted with the rest of the settings.filelock.Store.SetMaxAgehook: a policy lens consulted at liveness checks (Live/List/rename-carry) foruser-type locks only. Existing locks are affected immediately by a settings change, and turning the cap off revives them — the policy is never baked into stored records (save-time pruning still uses only a dav lock's ownExpires). Dav locks keep their RFC timeouts.main.gofrom the settings store; no restart needed.set-*field relocation), load/save through the existing merge-over-serverSettings PUT, i18n ×4.Closes #394.