From d7a8b29d387f6980c9eeeac45103fae2127e7220 Mon Sep 17 00:00:00 2001 From: Aleksey Bragin Date: Sun, 2 Jan 2005 17:46:36 +0000 Subject: [PATCH] Removed file/folder svn path=/trunk/; revision=12724 --- reactos/locks/db-logs.lock | 7 ------- reactos/locks/db.lock | 10 ---------- 2 files changed, 17 deletions(-) delete mode 100644 reactos/locks/db-logs.lock delete mode 100644 reactos/locks/db.lock diff --git a/reactos/locks/db-logs.lock b/reactos/locks/db-logs.lock deleted file mode 100644 index f6956f71265..00000000000 --- a/reactos/locks/db-logs.lock +++ /dev/null @@ -1,7 +0,0 @@ -DB logs lock file, representing locks on the versioned filesystem logs. - -All log manipulators of the repository's -Berkeley DB environment take out exclusive locks on this file -to ensure that only one accessor manupulates the logs at the time. - -You should never have to edit or remove this file. diff --git a/reactos/locks/db.lock b/reactos/locks/db.lock deleted file mode 100644 index 6269d7ef0db..00000000000 --- a/reactos/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.