From 69d24d869bf97978b31a51fe8e8d08cac4874d67 Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Tue, 21 Dec 1999 04:54:30 +0000 Subject: first cut at using the tdb code for the connections structure, the SWAT status page and smbstatus. It made the code _much_ simpler, I wish we'd done a database module a long time ago! (This used to be commit 4951755413c11d4c5b9af4699a6e622056d52433) --- source3/tdb/README | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'source3/tdb/README') diff --git a/source3/tdb/README b/source3/tdb/README index fc99a68acc..3c0059c5cb 100644 --- a/source3/tdb/README +++ b/source3/tdb/README @@ -11,7 +11,7 @@ Compilation ----------- add HAVE_MMAP=1 to use mmap instead of read/write -add TDB_DEBUG for verbose debug info +add TDB_DEBUG=1 for verbose debug info add NOLOCK=1 to disable locking code Testing @@ -21,6 +21,12 @@ Compile tdbtest.c and link with gdbm for testing. tdbtest will perform identical operations via tdb and gdbm then make sure the result is the same +Also included is tdbtool, which allows simple database manipulation +on the commandline. + +tdbtest and tdbtool are not built as part of Samba, but are included +for completeness. + Interface --------- @@ -31,3 +37,4 @@ The interface is very similar to gdbm except for the following: - no tdbm_reorganise() function - no tdbm_sync() function. No operations are cached in the library anyway - added a tdb_traverse() function for traversing the whole database + -- cgit