Added a comment
This commit is contained in:
parent
3513cf4edd
commit
bdbb78f4dc
1 changed files with 13 additions and 0 deletions
|
@ -0,0 +1,13 @@
|
|||
[[!comment format=mdwn
|
||||
username="http://joeyh.name/"
|
||||
ip="24.159.78.125"
|
||||
subject="comment 5"
|
||||
date="2014-05-23T14:34:34Z"
|
||||
content="""
|
||||
My point is that if the filesystem is rejecting all attempts to access it with \"permission denied\", it's hardly surprising that git-annex doesn't work, since nothing works. If running the assistant somehow causes the filesystem to get into this strange broken state, then you have a nice repoducible bug to report on the filesystem, I suppose. I don't see how it could be a bug in git-annex, since it is using only standard posix filesystem system calls, plus inotify.
|
||||
|
||||
Based on this, samba/CIFS does not support inotify: <http://stackoverflow.com/questions/8124617/getting-file-create-notifications-for-cifs-mount-in-linux>
|
||||
Thus, the assistant won't work on it.
|
||||
|
||||
If I were you, I'd set up git-annex repositories on local filesystems, and let it take care of the syncronosation, rather than using a networked filesystem.
|
||||
"""]]
|
Loading…
Reference in a new issue