[Date Prev][Date Next]
Re: (ITS#4511) DB_CONFIG not being updated by slapd
Eric Irrgang wrote:
> On Thu, 27 Apr 2006, Howard Chu wrote:
>> firstname.lastname@example.org wrote:
>>> On Thu, 27 Apr 2006 email@example.com wrote:
>> The slapd-bdb(5) manpage says explicitly:
>> The options set using this directive will only be written to the
>> *DB_CONFIG* file if no such file existed at server startup time.
>> There is no bug here, this feature works as intended.
> Okay. Sorry about that. This behavior is consistent with documentation.
> But shouldn't DB_CONFIG get values from cn=config rather than the other
> way around? I understand that it may not be relevant because if you have
> an inconsistent DB_CONFIG and slapd.conf then you've got other problems,
Yes, if your files are inconsistent you have other problems...
> but slapd(8c) says (for -F):
> If both -f and -F are
> specified, the config file will be read and converted
> to config directory format and written to the specified
> Should that be amended to say "config files" (plural) or "config file and
The main slapd doesn't know anything about DB_CONFIG. Only the bdb (and
hdb) backends deal with that, so there is no reason to mention them
here, and as you saw, the slapd-bdb(5) manpage already addresses DB_CONFIG.
Once again, I'll stress this point - once you convert to slapd.d format,
you are expected to use that configuration mechanism exclusively. The
intent is to be able to configure every aspect of slapd operation from
this single system. If you keep going back and making changes in
slapd.conf and DB_CONFIG directly you're just shooting yourself in the foot.
Once you have slapd.d setup, any LDAPModify operations on the
olcDBConfig attribute will be written out to the DB_CONFIG file, so
there is no good reason to modify it directly.
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/