[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
wrong ldbm flags ?
Hi,
maybe I'm overlooking something fundamental, but I guess you'll tell me.
Looking after the reasons for an index inconsistency, I've come across
the following:
When setting dbnolocking and/or dbnosync in back-ldbm/slapd.conf,
ldbm_cache_open() in dbcache.c sets flags to include either LDBM_LOCKING
or LDBM_NOLOCKING resp. LDBM_SYNC/LDBM_NOSYNC.
But include/ldbm.h sets (we use Berkeley DB 3.1 like everyone):
#define LDBM_NOSYNC 0
#define LDBM_SYNC 0
#define LDBM_LOCKING 0
#define LDBM_NOLOCKING 0
So setting dbnolocking/dbnosync does not make any difference !?
By the way, does it make sense to pass the DB_INIT_TXN and DB_RECOVER
to ldbm_open. While this won't provide true LDAP transactions, my understanding
is that it should ensure database consistency on crashes.
regards,
Markus
begin:vcard
n:Storm;Markus
tel;fax:++49 +5241 80-67867
tel;work:++49 +5241 80-7867
x-mozilla-html:FALSE
org:mediaWays GmbH;NMW-T
adr:;;Postfach 185;Guetersloh;;33311;Germany
version:2.1
email;internet:Markus.Storm@mediaWays.net
x-mozilla-cpt:ils.mediaways.net;23744
fn:Markus Storm
end:vcard