diff options
| author |  yarikoptic <yarikoptic@web> | 2017-02-10 01:38:33 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-02-10 01:38:33 +0000 |
| commit | 0389fab232fa3a1a3dca84be6b6024667764ac4c (patch) | |
| tree | f270c94b130857f70409e02253a0c7e1d1a164fc | |
| parent | b85fb0fc834efaf676214065d20947d10c4fd2d7 (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/git_annex_info_fails_on_NFS__58___waitToSetLock__58___resource_exhausted___40__No_locks_available__41__/comment_2_4c2e143b8b3283734963e0a6e68755ac._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_info_fails_on_NFS__58___waitToSetLock__58___resource_exhausted___40__No_locks_available__41__/comment_2_4c2e143b8b3283734963e0a6e68755ac._comment b/doc/bugs/git_annex_info_fails_on_NFS__58___waitToSetLock__58___resource_exhausted___40__No_locks_available__41__/comment_2_4c2e143b8b3283734963e0a6e68755ac._comment new file mode 100644 index 000000000..9fd9af650 --- /dev/null +++ b/doc/bugs/git_annex_info_fails_on_NFS__58___waitToSetLock__58___resource_exhausted___40__No_locks_available__41__/comment_2_4c2e143b8b3283734963e0a6e68755ac._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 2" + date="2017-02-10T01:38:33Z" + content=""" +indeed that was the case.... not clear though how that one ended up without pidlock not being set since all creation was uniform as far as I remember + +I wonder if annex could potentially detect for such a case and reissue check/assignment of the pidlock? +"""]] |