On Thursday 10 March 2005 20:53, Dan Melomedman shaped the electrons to say: <snip> > If you still want to use 2.x.x version, then I strongly recommend NOT > using the Berkely DB backend. Use GDBM instead,
I would argue against using GDBM because of the sheer stability and data corruption that we have experienced with this backend. I currently use berkely ldbm which has been very stable but unfortunately there is no more development with ldbm backend. > you'll reduce the number > of future database corruptions dramatically. You will also avoid the > bulk of the bugs and Berkeley DB management overhead. If you've been > hanging around the OpenLDAP mailing lists, you'll see many responses > from OpenLDAP developers such as "This isn't our problem, this is > Berkeley DB problem, go fix it instead". I used 2.1.30 with bdb backend and had no end of troubles. Data Corruption and memory leaks. So I am quite relictant to change to bdb just yet. The transactional logging is obviously a good feature that we could use, however, the stability for us was far more important. -- slr. b0n0b0 #qmail on efnet key: 0x0B65ABDC - http://wwwkeys.pgp.net:11371
