mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

pid locking configuration and abstraction layer for git-annex

Browse source 
(not actually used anywhere yet)
This commit is contained in:
Joey Hess 2015-11-12 17:47:31 -04:00
parent 77b490bfba
commit aa4192aea6
Failed to extract signature
7 changed files with 131 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

24
doc/git-annex.mdwn
View file

@ -965,6 +965,30 @@ Here are all the supported configuration settings.
which does not support symbolic links, or hard links, or unix permissions.
This is automatically probed by "git annex init".
* `annex.pidlock`
Normally, git-annex uses fine-grained lock files to allow multiple
processes to run concurrently without getting in each others' way.
That works great, unless you are using git-annex on a filesystem that
does not support POSIX fcntl locks. This is sometimes the case when
using NFS or Lustre filesystems.
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..)
* `annex.pidlocktimeout`
When using pid lock files, it's possible for a stale lock file to get
left behind by previous run of git-annex that crashed or was interrupted.
This is mostly avoided, but can occur especially when using a network
file system.
git-annex will wait up to this many seconds for the pid lock
file to go away, and will then abort if it cannot continue. Default: 300
* `remote.<name>.annex-cost`
When determining which repository to