git-annex/Types/LockCache.hs

{- git-annex lock cache data types
 - 
 - Copyright 2014 Joey Hess <id@joeyh.name>
 -
 - Licensed under the GNU AGPL version 3 or higher.
 -}

module Types.LockCache (
	LockCache,
	LockHandle
) where

import qualified Data.Map as M
import Utility.LockPool (LockHandle)

type LockCache = M.Map FilePath LockHandle
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. 2015-05-18 20:23:07 +00:00			`{- git-annex lock cache data types`
use locking on Windows This is all the easy cases, where there was already a separate lock file. 2014-01-28 18:17:14 +00:00			`-`
update my email address and homepage url 2015-01-21 16:50:09 +00:00			`- Copyright 2014 Joey Hess <id@joeyh.name>`
use locking on Windows This is all the easy cases, where there was already a separate lock file. 2014-01-28 18:17:14 +00:00			`-`
update licenses from GPL to AGPL This does not change the overall license of the git-annex program, which was already AGPL due to a number of sources files being AGPL already. Legally speaking, I'm adding a new license under which these files are now available; I already released their current contents under the GPL license. Now they're dual licensed GPL and AGPL. However, I intend for all my future changes to these files to only be released under the AGPL license, and I won't be tracking the dual licensing status, so I'm simply changing the license statement to say it's AGPL. (In some cases, others wrote parts of the code of a file and released it under the GPL; but in all cases I have contributed a significant portion of the code in each file and it's that code that is getting the AGPL license; the GPL license of other contributors allows combining with AGPL code.) 2019-03-13 19:48:14 +00:00			`- Licensed under the GNU AGPL version 3 or higher.`
use locking on Windows This is all the easy cases, where there was already a separate lock file. 2014-01-28 18:17:14 +00:00			`-}`

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. 2015-05-18 20:23:07 +00:00			`module Types.LockCache (`
			`LockCache,`
use locking on Windows This is all the easy cases, where there was already a separate lock file. 2014-01-28 18:17:14 +00:00			`LockHandle`
			`) where`

			`import qualified Data.Map as M`
convert from Utility.LockPool to Annex.LockPool everywhere 2015-11-12 22:05:45 +00:00			`import Utility.LockPool (LockHandle)`
use locking on Windows This is all the easy cases, where there was already a separate lock file. 2014-01-28 18:17:14 +00:00
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. 2015-05-18 20:23:07 +00:00			`type LockCache = M.Map FilePath LockHandle`