Re: (ITS#4511) DB_CONFIG not being updated by slapd

[erici@motown.cc.utexas.edu]

On Thu, 27 Apr 2006, Howard Chu wrote:

>erici@motown.cc.utexas.edu wrote:
>> On Thu, 27 Apr 2006 quanah@stanford.edu 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,
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
          directory.

Should that be amended to say "config files" (plural) or "config file and
DB_CONFIG"?

Or is that covered by the paragraph from slapd-bdb(5)?

     It is noted that these options are  intended  to  complement
     Berkeley  DB  configuration options set in the environment's
     DB_CONFIG file.  See Berkeley DB documentation  for  details
     on DB_CONFIG configuration options.  Where there is overlap,
     settings in DB_CONFIG take precedence.

Sorry for missing that bit about DB_CONFIG creation.  I guess my memory
was corrupted...

-- 
Eric Irrgang - UT Austin ITS Unix Systems - (512)475-9342