summaryrefslogtreecommitdiff
path: root/bugs/chunks-dir-init-has-no-lock.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'bugs/chunks-dir-init-has-no-lock.mdwn')
-rw-r--r--bugs/chunks-dir-init-has-no-lock.mdwn14
1 files changed, 0 insertions, 14 deletions
diff --git a/bugs/chunks-dir-init-has-no-lock.mdwn b/bugs/chunks-dir-init-has-no-lock.mdwn
deleted file mode 100644
index 36402d6..0000000
--- a/bugs/chunks-dir-init-has-no-lock.mdwn
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!tag obnam-1.0-blocker]]
-
-When Obnam initializes the `chunks` directory, for encryption, it is
-done without locking. That's a race condition: two clients started
-at the same time against an empty directory may result in both of
-them creating the same files.
-
-Normal use of the `chunks` directory does not need locking: clients
-are free to create new chunks files there, as long as they take care
-to not overwrite existing files.
-
---liw
-
-[[done]] in bzr