diff options
| author | Lars Wirzenius <liw@liw.fi> | 2014-04-16 07:52:18 +0100 |
|---|---|---|
| committer | Lars Wirzenius <liw@liw.fi> | 2014-04-16 07:52:18 +0100 |
| commit | c6672776b363cfc23f9a73000e918fa893a26b37 (patch) | |
| tree | b5bdcc47b40a29cd92fa95447bb212e3b2b48fc5 /yarns/9000-implements.yarn | |
| parent | 2bc881db5fba2fcff507cc9e418600f77d37d747 (diff) | |
| download | obnam-c6672776b363cfc23f9a73000e918fa893a26b37.tar.gz | |
Add scenario for forcing locks open
Diffstat (limited to 'yarns/9000-implements.yarn')
| -rw-r--r-- | yarns/9000-implements.yarn | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/yarns/9000-implements.yarn b/yarns/9000-implements.yarn index bda6d3c8..1a86fbe7 100644 --- a/yarns/9000-implements.yarn +++ b/yarns/9000-implements.yarn @@ -456,6 +456,21 @@ Forget a key from the user's keyring. fingerprint="$(get_fingerprint "$MATCH_2")" gpg --batch --delete-secret-key "$fingerprint" + +Lock management +--------------- + +We need to lock parts of the repository, and force those locks open. + + IMPLEMENTS WHEN user (\S+) locks repository (\S+) + run_obnam "$MATCH_1" -r "$DATADIR/$MATCH_2" _lock + +Force it open. + + IMPLEMENTS WHEN user (\S+) forces open the lock on repository (\S+) + run_obnam "$MATCH_1" -r "$DATADIR/$MATCH_2" force-lock + + Client management ----------------- |