From a70d65ea7fc37167f461e5af3fd0d4e61162da1b Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Tue, 11 Jun 2013 15:09:44 +0000 Subject: [PATCH] Added a comment --- ...ment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment diff --git a/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment new file mode 100644 index 0000000000..54f533a926 --- /dev/null +++ b/doc/bugs/file_access__47__locking_issues_with_the_assitant/comment_6_4ce243cb0ea8ff810a4949a5320e4afc._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 6" + date="2013-06-11T15:09:44Z" + content=""" +No. Direct mode makes this kind of problem less likely to occur. + +Are you only seeing this problem on OSX? + +My guess, which is only a guess at this point is that while direct mode leaves files in-place etc, which should avoid this kind of problem, it does mess with their permissions berifly when ingesting them into the annex. The write bit is breifly turned off, +while it checks that nothing currently has the file open to be written. +"""]]