aboutsummaryrefslogtreecommitdiff
path: root/doc/git-annex.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-11-13 15:55:16 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-11-13 15:55:16 -0400
commitad551119667aae6bb84716f4625484823a7ea652 (patch)
tree6b7d402ffcde9eafc5b93c3b85684f6929340d61 /doc/git-annex.mdwn
parentc006d97f0cb4a5b4f19d9faca9205a5081d54c67 (diff)
more warnings about networked filesystems
Diffstat (limited to 'doc/git-annex.mdwn')
-rw-r--r--doc/git-annex.mdwn6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/git-annex.mdwn b/doc/git-annex.mdwn
index c28d8af6c..fca499a7e 100644
--- a/doc/git-annex.mdwn
+++ b/doc/git-annex.mdwn
@@ -976,8 +976,10 @@ Here are all the supported configuration settings.
To support such situations, you can set annex.pidlock to true, and it
will fall back to a single top-level pid file lock.
- (Although, often, you'd really be better off fixing your networked
- filesystem configuration to support POSIX locks..)
+ Although, often, you'd really be better off fixing your networked
+ filesystem configuration to support POSIX locks.. And, some networked
+ filesystems are so inconsistent that one node can't reliably tell when
+ the other node is holding a pid lock. Caveat emptor.
* `annex.pidlocktimeout`