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

[erici@motown.cc.utexas.edu]

On Thu, 27 Apr 2006 quanah@stanford.edu wrote:

>Quoting erici@motown.cc.utexas.edu:
>
>> Full_Name: Eric Irrgang
>> Version: 2.3.21
>> OS: Solaris 9 sparcv9
>> URL:
>> Submission from: (NULL) (128.83.217.14)
>>
>>
>> Once it exists, DB_CONFIG never gets updated regardless of whether or not
>> its content agrees with what slapd.conf says it should be.  However, if
>> DB_CONFIG has an mtime more recent than the last slapd run, slapd reports
>> "bdb_db_open: DB_CONFIG for suffix dc=entdir,dc=utexas,dc=edu has
>> changed.
>> Performing database recovery to activate new settings." but does nothing
>> to write a new DB_CONFIG.  If slapd.d does not yet have the back-ldif
>> files for cn=config, then the olcDatabase{1}bdb.ldif file is created with
>> "olcDbConfig: {0}set_shm_key #" from the DB_CONFIG file and
>> "olcDbShmKey: #" from the slapd.conf file.
>
>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.

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