> Experience told me that it is very important for BDB backend stability > to have a DB_CONFIG file in the database path. > > I modified a bit /etc/init.d/slapd so that it checks the presence of > this file. Please find attached the patch.
I'm not sure if this is still worth doing or not with the current package. OpenLDAP will now write out a DB_CONFIG file for you based on the dbconfig options in slapd.conf if you have them, and the current slapd.conf for any new installation includes those options. Also, the package will write a DB_CONFIG file by default for new installations *and* for any installation in which we have to dump and reload the database. So this warning would only be for people with old configurations and old databases but who haven't upgraded through an upgrade that requires dumping and reloading the database. That seems like a fairly small set of people. I suppose the check and warning doesn't hurt anything, but I'm kind of ambivalent about committing it. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
