From 06415e68bc0a5df3c4c509151a474e0a901c7c64 Mon Sep 17 00:00:00 2001 From: Sree Harsha Totakura Date: Tue, 15 May 2012 16:14:04 +0000 Subject: [PATCH] -doc header --- src/lockmanager/README | 11 ----------- src/lockmanager/test_lockmanager_api_servercrash.c | 4 ++-- 2 files changed, 2 insertions(+), 13 deletions(-) delete mode 100644 src/lockmanager/README diff --git a/src/lockmanager/README b/src/lockmanager/README deleted file mode 100644 index 8d9339e4d..000000000 --- a/src/lockmanager/README +++ /dev/null @@ -1,11 +0,0 @@ -The lockmanager service serves as a global locker for other gnunet -programs. This service eliminates the need for programs to maintain their own -checks upon a resource which should be protected from concurrent access. - -Locking is managed through locking-domains. A locking-domain is a string which -uniquely identifies a group of locks. Locks are represented as unsigned 32-bit -integers. When a critical resource has to be protected against simulataneous -access by 2 programs, both of them should connect to the lockmanager using the -same locking-domain and try to acquire a lock with the same number. Since only -one of them can acquire the lock the other will be denied locking until the -it the lock is released. \ No newline at end of file diff --git a/src/lockmanager/test_lockmanager_api_servercrash.c b/src/lockmanager/test_lockmanager_api_servercrash.c index 71e5f421d..4b9d9cbe4 100644 --- a/src/lockmanager/test_lockmanager_api_servercrash.c +++ b/src/lockmanager/test_lockmanager_api_servercrash.c @@ -19,8 +19,8 @@ */ /** - * @file lockmanager/test_lockmanager_api_lockrelease.c - * @brief Test cases for lockmanager_api where client disconnects abruptly + * @file lockmanager/test_lockmanager_api_servercrash.c + * @brief Test cases for lockmanager_api where the server crashes * @author Sree Harsha Totakura */ -- 2.25.1