summaryrefslogtreecommitdiffstats
path: root/locks/db.lock
diff options
context:
space:
mode:
authorOliver Schinagl <oliver@schinagl.nl>2005-04-07 07:33:28 (GMT)
committerOliver Schinagl <oliver@schinagl.nl>2005-04-07 07:33:28 (GMT)
commit08bf8216aa4a94bb2fa85a52a9b3eb5e9b3a0ff8 (patch)
tree63bf6b8f10d9190553ffd52dfaab7c83fb392ea8 /locks/db.lock
parent2c46418afca5734bbf8e87dba551e7b868bd76af (diff)
download5kk53-08bf8216aa4a94bb2fa85a52a9b3eb5e9b3a0ff8.zip
5kk53-08bf8216aa4a94bb2fa85a52a9b3eb5e9b3a0ff8.tar.gz
5kk53-08bf8216aa4a94bb2fa85a52a9b3eb5e9b3a0ff8.tar.bz2
Diffstat (limited to 'locks/db.lock')
-rw-r--r--locks/db.lock10
1 files changed, 10 insertions, 0 deletions
diff --git a/locks/db.lock b/locks/db.lock
new file mode 100644
index 0000000..6269d7e
--- /dev/null
+++ b/locks/db.lock
@@ -0,0 +1,10 @@
+DB lock file, representing locks on the versioned filesystem.
+
+All accessors -- both readers and writers -- of the repository's
+Berkeley DB environment take out shared locks on this file, and
+each accessor removes its lock when done. If and when the DB
+recovery procedure is run, the recovery code takes out an
+exclusive lock on this file, so we can be sure no one else is
+using the DB during the recovery.
+
+You should never have to edit or remove this file.