more warnings about networked filesystems
authorJoey Hess <joeyh@joeyh.name>
Fri, 13 Nov 2015 19:55:16 +0000 (15:55 -0400)
committerJoey Hess <joeyh@joeyh.name>
Fri, 13 Nov 2015 19:55:16 +0000 (15:55 -0400)
doc/git-annex.mdwn

index c28d8af6c07047abda808050741674b583b63aa0..fca499a7eb1db849c3b4baf34118e05cf2f2d005 100644 (file)
@@ -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`