summaryrefslogtreecommitdiff
path: root/obnam.1.in
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2016-02-12 13:51:50 +0200
committerLars Wirzenius <liw@liw.fi>2016-02-12 13:54:50 +0200
commit0b3ccc928a56a3ee5ab29a87e2f24e053896017f (patch)
treec5907ba57200d31455af9a819f11b3e2c17d6f36 /obnam.1.in
parentd892d31c87d342b5c728b439756bd075bc602e6e (diff)
downloadobnam-0b3ccc928a56a3ee5ab29a87e2f24e053896017f.tar.gz
Fix description of force-lock: always all locks
Diffstat (limited to 'obnam.1.in')
-rw-r--r--obnam.1.in10
1 files changed, 5 insertions, 5 deletions
diff --git a/obnam.1.in b/obnam.1.in
index 8a2de45f..d825adbe 100644
--- a/obnam.1.in
+++ b/obnam.1.in
@@ -103,11 +103,11 @@ all file contents still exists in the backup repository.
It may take quite a long time to run.
.IP \(bu
.B force\-lock
-removes a lock file for a client in the repository.
-You should only force a lock if you are sure no-one is accessing that
-client's data in the repository.
-A dangling lock might happen, for example, if obnam loses its network
-connection to the backup repository.
+removes lock files for aall clients in the repository.
+You should only force a lock if you are sure no client is accessing
+the repository.
+A dangling lock might happen, for example,
+if "obnam backup" loses its network connection to the backup repository.
.IP \(bu
.B client\-keys
lists the encryption key associated with each client.