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

[hyc@symas.com]

erici@motown.cc.utexas.edu wrote:
> On Thu, 27 Apr 2006 quanah@stanford.edu wrote:
>
>   
>> I think you are confusing some different things.
>> If DB_CONFIG exists, the db* parameters in slapd.conf are ignored.  If
>> DB_CONFIG doesn't exist, it is created with those parameters.
>>
>> If the DB_CONFIG file in the database directory has had a timestamp change,
>> alock will detect that, and run db recovery on slapd startup.
>>
>> I'm not clear why you have shm settings in both DB_CONFIG and slapd.conf.
>> Generally you should only have that set in slapd.conf, IIRC.
>>     
>
> Well, the DB_CONFIG file was generated by the slapd from slapd.conf
> initially.  Then slapd.conf was modified.  Then slapd was started with the
> addition of '-F' and slapd.d was built with values from two sources.
>
>   
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.

-- 
  -- 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/