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

Added a comment

Browse source
This commit is contained in:
https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4 2016-03-10 04:36:12 +00:00 • committed by admin
parent ea57543394
commit 7ca35b766f
1 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/bugs/git-annex:_content_is_locked__while_trying_to_move_under_NFS_and_pidlock/comment_12_d499a2f44e8ee2f39ee959f4d6373570._comment Normal file
View file

@ -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 ;)
"""]]