RE: growth pains, ldbm or bdb?

["Howard Chu" <hyc@highlandsun.com>]

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Micah Anderson

> We've been merrily going about our way with our
> pam/courier/postfix/nss ldap implementation using ldbm, until recently
> when things started to get nasty. I dont know if we reached a growth
> point, or if we have some internal datastructure corruption, but our
> slapd keeps dying on us, and I am guessing that our ldbm files get
> corrupted when the machine crashes (I run db3_recover on them
> afterwards, but it always is pretty nondescript messages:
> db_recover: Recovery complete at Fri Jan 16 21:19:18 2004
> db_recover: Maximum transaction id 80000000 Recovery checkpoint [0][0]
> making me feel like nothing is happening).

Read the FAQ and the archives of this list.

Note that db_recover does nothing at all for an ldbm database. There are no
error recovery mechanisms for back-ldbm. That's one very good reason not to
use it...

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support