summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4 <https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4@web>2016-03-10 04:36:12 +0000
committerGravatar admin <admin@branchable.com>2016-03-10 04:36:12 +0000
commit1e373c8cf258704ab5c319bc42e649c45b0da17a (patch)
tree2d6c23db63660ca3afced356fd5846f04fdec9b3
parent0dc97721e64616e0c254ce42eefc58888650d14f (diff)
Added a comment
-rw-r--r--doc/bugs/git-annex:_content_is_locked__while_trying_to_move_under_NFS_and_pidlock/comment_12_d499a2f44e8ee2f39ee959f4d6373570._comment13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/git-annex:_content_is_locked__while_trying_to_move_under_NFS_and_pidlock/comment_12_d499a2f44e8ee2f39ee959f4d6373570._comment b/doc/bugs/git-annex:_content_is_locked__while_trying_to_move_under_NFS_and_pidlock/comment_12_d499a2f44e8ee2f39ee959f4d6373570._comment
new file mode 100644
index 000000000..5ab7c9e11
--- /dev/null
+++ b/doc/bugs/git-annex:_content_is_locked__while_trying_to_move_under_NFS_and_pidlock/comment_12_d499a2f44e8ee2f39ee959f4d6373570._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4"
+ subject="comment 12"
+ date="2016-03-10T04:36:12Z"
+ content="""
+so -- shouldn't annex at least upon init sense if repo is under nfs? if to be done platform independent way then it could do smth like
+
+[[!format sh \"\"\"
+python -c 'from glob import glob; import os; f=open(\".tmp-test\", \"w\"); os.unlink(\".tmp-test\"); assert(not glob(\".nfs*\"))'
+\"\"\"]]
+
+somewhere under .git/annex/tmp .. so if .nfs* file gets generated -- under nfs. Seems to work for me in limited set of tests -- assertion fails all the time under NFS ;)
+"""]]