[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#5134) dbconfig vs. DB_CONFIG

ghenry@suretecsystems.com wrote:

>> I think the point is not what the code should (or should not) do, or
>> whether its current behavior is correct or not; it's rather that the man
>> page, as far as I understand it, is not clear about what the code
>> currently does.
> Ok, well the text should reflect what the code does. I think I'm missing
> the  point of your question. If the text doesn't currently match what is
> actually  happening in the code, then we fix the man page so it does.

My point is that from that text I don't understand what the code does.
Either it's my English (could well be), or it needs to be reworded.  I'm
quoting here the original text:


       dbconfig <Berkeley-DB-setting>
       Specify a configuration directive to be placed in the DB_CONFIG
       file of the database directory. The dbconfig directive is  just
       a convenience to allow all necessary configuration to be set in
       the slapd.conf file.  The options set using this directive will
       only  be  written to the DB_CONFIG file if no such file existed
       at server startup time. This allows one to set  initial  values
       without   overwriting/destroying  a  DB_CONFIG  file  that  was
       already customized through other means.


So it seems to be quite clear about what's going to happen if no
DB_CONFIG exists, but not as clear about what happens if DB_CONFIG
already exists, apart from not getting overwritten or otherwise modified.


Ing. Pierangelo Masarati
OpenLDAP Core Team

SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
Office:  +39 02 23998309
Mobile:  +39 333 4963172
Email:   pierangelo.masarati@sys-net.it