diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-02-10 14:51:50 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-02-10 14:51:50 -0400 |
| commit | 25958421abda59fa77fc4bd422ba7878f04f9809 (patch) | |
| tree | 8f6d38338370391e9d55196695115bd0ae4721c0 /doc | |
| parent | 46a3ea4daccc5efec804c359fa80f42022d8457b (diff) | |
comment
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/git_annex_init_timeout/comment_1_e456f5367af5a5a3a31fc982952079e3._comment | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/forum/git_annex_init_timeout/comment_1_e456f5367af5a5a3a31fc982952079e3._comment b/doc/forum/git_annex_init_timeout/comment_1_e456f5367af5a5a3a31fc982952079e3._comment new file mode 100644 index 000000000..06aed071a --- /dev/null +++ b/doc/forum/git_annex_init_timeout/comment_1_e456f5367af5a5a3a31fc982952079e3._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2017-02-10T18:06:28Z" + content=""" +git-annex needs flock locking to be supported by the filesystem it's used +on. There's a workaround using pid locks, but that is apparently not +working on OSX in your case. I've only tested it on Linux. + +I tried reproducing this on OSX by enabling annex.pidlock before using +git-annex. But it worked ok. + +So, I suspect there may be a problem with the network filesystem's handling +of the pidlock file. One likely problem is if it doesn't support hard +links, since the pidlock file is hard linked into place. + +You can check if it supports hard links by running this on the drive where +you had the problem: + + touch foo + ln foo bar +"""]] |