aboutsummaryrefslogtreecommitdiff
path: root/Utility/LockFile.hs
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-05-18 16:23:07 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-05-19 14:09:52 -0400
commitae5433c4caf0ee57e3338df6dcd625f20ece7101 (patch)
tree5bdab44419df36e7e5aab2e36cd6b221654de04e /Utility/LockFile.hs
parent94a3e606fb31150c969d63790ec1ef870f413cc1 (diff)
use lock pools throughout git-annex
The one exception is in Utility.Daemon. As long as a process only daemonizes once, which seems reasonable, and as long as it avoids calling checkDaemon once it's already running as a daemon, the fcntl locking gotchas won't be a problem there. Annex.LockFile has it's own separate lock pool layer, which has been renamed to LockCache. This is a persistent cache of locks that persist until closed. This is not quite done; lockContent stil needs to be converted.
Diffstat (limited to 'Utility/LockFile.hs')
-rw-r--r--Utility/LockFile.hs3
1 files changed, 3 insertions, 0 deletions
diff --git a/Utility/LockFile.hs b/Utility/LockFile.hs
index f9a0e6783..1d924fc1e 100644
--- a/Utility/LockFile.hs
+++ b/Utility/LockFile.hs
@@ -4,6 +4,9 @@
- This module does *not* attempt to be a portability shim, it just exposes
- the native locking of the OS.
-
+ - Posix fcntl locks have some gotchas. So, consider using
+ - Utility.LockPool instead of using this module directly.
+ -
- Copyright 2014 Joey Hess <id@joeyh.name>
-
- License: BSD-2-clause