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

Display a message when git-annex has to wait for a pid lock file held by another process

Browse source
This commit is contained in:
Joey Hess 2020-08-26 13:05:34 -04:00
parent b24ba92231
commit b68f214312
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
7 changed files with 69 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

7
doc/bugs/get_is_stuck_unless_a_clone_was_previously_explicitly___34__annex_init__34__ed/comment_7_21dbdbf7e4e889dc7c2475a0b9d4c5d7._comment Normal file
View file

@ -0,0 +1,7 @@
[[!comment format=mdwn
username="joey"
subject="""comment 7"""
date="2020-08-26T17:02:26Z"
content="""
Added that message after the first second waiting on a pid lock.
"""]]

9
doc/git-annex.mdwn
View file

@ -1186,14 +1186,15 @@ Like other git commands, git-annex is configured via `.git/config`.
the other node is holding a pid lock. Caveat emptor.
* `annex.pidlocktimeout`
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
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
file system. This timeout prevents git-annex waiting forever in such a
situation.
* `annex.cachecreds`