summaryrefslogtreecommitdiffstats
path: root/locks/db.lock
diff options
context:
space:
mode:
authorOliver Schinagl <oliver@schinagl.nl>2005-04-11 11:38:46 (GMT)
committerOliver Schinagl <oliver@schinagl.nl>2005-04-11 11:38:46 (GMT)
commitbab5d35fb20688a6c9df8dd2dcad8ca4859aef90 (patch)
tree2929dee8ade508dad9e6e327e24f7ade4df273a9 /locks/db.lock
parent8cca58d4f4a6db7f370f2f6f6c6b50de9af302e9 (diff)
download5kk53-bab5d35fb20688a6c9df8dd2dcad8ca4859aef90.zip
5kk53-bab5d35fb20688a6c9df8dd2dcad8ca4859aef90.tar.gz
5kk53-bab5d35fb20688a6c9df8dd2dcad8ca4859aef90.tar.bz2
Deleted some crap someone added.
Diffstat (limited to 'locks/db.lock')
-rw-r--r--locks/db.lock10
1 files changed, 0 insertions, 10 deletions
diff --git a/locks/db.lock b/locks/db.lock
deleted file mode 100644
index 6269d7e..0000000
--- a/locks/db.lock
+++ /dev/null
@@ -1,10 +0,0 @@
-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.