From e15907f13889ab28bccf6a56e01f693044c08fba Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 8 Oct 2019 15:39:58 -0400 Subject: [PATCH] response --- ...nt_4_7255d87f5802a8d12204e4afc797070d._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/git-annex-watch_clarification/comment_4_7255d87f5802a8d12204e4afc797070d._comment diff --git a/doc/forum/git-annex-watch_clarification/comment_4_7255d87f5802a8d12204e4afc797070d._comment b/doc/forum/git-annex-watch_clarification/comment_4_7255d87f5802a8d12204e4afc797070d._comment new file mode 100644 index 0000000000..e0b511e22d --- /dev/null +++ b/doc/forum/git-annex-watch_clarification/comment_4_7255d87f5802a8d12204e4afc797070d._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2019-10-08T19:33:39Z" + content=""" +It does not, mostly because it would need to run lsof once per file, which +would be significantly expensive. The daemon is able to batch changes and +so run lsof less often. + +However, git-annex add does detect if a file is modified while it's being +hashed, and will avoid adding it then. And it prevents against most ways +the file could be modified except for if something has it open for write +beforehand. In the worst case, the object in the annex gets written to, +which later gets detected by fsck. +"""]]