Jason Dusek wrote:

I've added two seemingly innocuous lines to my LDAP configuration:

Index: conf-root/etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif

--- etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif (revision 1444) +++ etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif (working copy) @@ -1,6 +1,9 @@ dn: olcDatabase={1}bdb objectClass: olcDatabaseConfig objectClass: olcBdbConfig +objectClass: olcSyncProvConfig +olcSpCheckpoint: 100 5 +olcSpSessionlog: 100 olcDatabase: {1}bdb olcSuffix: dc=metascopic,dc=com olcAccess: {0}to attrs=userPassword

However, they cause `slaptest` to segfault on Linux! I'm a little perplexed by this.

How can you tell that the above configuration is correct? olcDatabaseConfig and olcSyncProvConfig are both structural objectClasses, and thus cannot live in the same entry. Besides this, back-config cannot be considered just a regular database, since data it contains triggers specific code execution. The fact that manually hacking database files leads to a segfault is a pity, as this error could be better handled (you may file an ITS, for what is worth), but the culprit is mucking with files.

:; slaptest -F etc/openldap/slapd.d/ Segmentation fault

Removing the lines restores `slaptest` to a state of sanity.

Not a surprise.

p.

Ing. Pierangelo Masarati OpenLDAP Core Team

SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando@sys-net.it -----------------------------------