On Fri, Apr 15, 2005 at 01:30:33PM +0900, Christian Balzer wrote: > > Steve Langasek wrote: > > >On Fri, Apr 15, 2005 at 12:09:19PM +0900, Christian Balzer wrote: > > >> Changes are generated by ldifsort.pl/ldifdiff.pl and then applied with > >> ldapmodify for a low impact and smooth operation, using ldbm as > >> backend.
> >The previous version of slapd *also* had corruption issues, and this is the > >driving reason for putting slapd 2.2 in sarge. > I read that and I'm all for using current versions of software when > getting near to a Debian release. > Alas it's hard to contrast one year of trouble free operation with > the current state of affairs. A fix that breaks all the users which > until now had a perfectly working setup is, well, not a fix. > Or to put it quite blunt, people encountering DB corruption with > the previous version most likely did NOT run production systems with it. > Me and others on the other hand... > >Which LDAP backend are you using for this directory? > See above, LDBM (whatever actual DB that defaults to these days). Sorry, I missed that. I would strongly encourage you to switch to BDB, which is the recommended backend for OpenLDAP 2.2; LDBM was more stable in 2.1 because BDB itself was *un*stable, but in 2.2, BDB is reportedly quite solid whereas LDBM is less stable than it had been in 2.1. > I loathe BDB for the times it takes for massive adds/modifies. > Even with slapadd, which takes about 2 minutes to load the entire DB > using ldbm as backend, but about 50 minutes with BDB. OpenLDAP 2.2 includes a '-q' option to slapadd that makes the load time much quicker by disabling checks that are unnecessary while loading a fresh db. This option will be enabled by default on database reloads in the slapd install scripts. -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
