| Summary: | Changing default database | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Anne Nicolas <ennael1> |
| Component: | RPM Packages | Assignee: | Buchan Milne test 2 <bgmilne> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | bgmilne, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | openldap | CVE: | |
| Status comment: | |||
|
Description
Anne Nicolas
2011-09-24 13:41:04 CEST
Where is a statement from the OpenLDAP project indicating that BDB is deprecated? Coverage of BDB still appears in the 2.4 Admin Guide: http://www.openldap.org/doc/admin24/slapdconf2.html#BDB%20and%20HDB%20Database%20Directives Since I experienced some 'funny' behaviour (entries present in the databasebut with incorrect DN due to hierchical links having been messed up) in 2.3.x, maybe I still have something against hdb ... Anyway, future development seems to be on a new database backend, mdb, which provides good performance on any size database with much less (read: no) tuning (whereas on both bdb and hdb significant effort is required for tuning a large multi-database environment). What *is* 'deprecated' according to the docs is slapd.conf: http://www.openldap.org/doc/admin24/slapdconf2.html "The older style slapd.conf(5) file is still supported, but its use is deprecated and support for it will be withdrawn in a future OpenLDAP release." However, at present, many answers on the mailing lists about configuring via cn=config suggest bootstrapping from a slapd.conf, which we have automated 'service ldap stop && service ldap convert && service ldap start' should be enough to do it. So, this may be more a matter of just calling 'service ldap convert' at the end of /usr/share/openldap/scripts/mandriva-dit-setup.sh CC:
(none) =>
bgmilne Pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED. @ Buchan Please set status to ASSIGNED. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. CC:
(none) =>
marja11 3-monthly ping As an update, I note that mdb, a new backend which does not use Berkeley DB, and as such avoids some of the tuning complications (especially with multiple databases) is probably the best option in the future, but is currently (2.4.30) still experimental. I see no real reason to switch to hdb now, when mdb is definitely the better option in future, and bdb is still supported. Status:
NEW =>
ASSIGNED ok thanks for the details. Let see that for Mageia 3. Closing it. Status:
ASSIGNED =>
RESOLVED |