summaryrefslogtreecommitdiff
path: root/doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-06-12 14:02:31 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-06-12 14:02:31 -0400
commite0c49de4bd8fef08ed40d3e43c4f08949f47e6e9 (patch)
tree55f76f41b860ae8bc24b9034ca1954822acf962b /doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn
parent871b79ceb7703c39a7e7eb3e043ac94c596bd1a3 (diff)
Direct mode: No longer temporarily remove write permission bit of files when adding them.
This write permission frobbing is very appropriate in indirect mode, since annexed objects are stored as immutably as can be managed. But not in direct mode, where files should be able to be modified at any time. There are already sufficient guards that there's no need to prevent a file being written to while it's being ingested, in direct mode. The inode cache will detect (most) types of modifications, and the add will fail. Then a re-add should be done. The assistant should get another inotify change event, and automatically add the new version of the file.
Diffstat (limited to 'doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn')
-rw-r--r--doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn b/doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn
index 2356c01fa..701536844 100644
--- a/doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn
+++ b/doc/bugs/file_access__47__locking_issues_with_the_assitant.mdwn
@@ -49,3 +49,6 @@ add www.cmt.mhs.man.ac.uk/admin_guide_cmt.log (checksum...) ok
# End of transcript or log.
"""]]
+
+> Ok, I was able to remove the write bit fiddling in direct mode. [[done]]
+> --[[Joey]]