<quote who="ando@sys-net.it">

ghenry@suretecsystems.com wrote:

...

...

The slapd-bdb(5) man page seems to me unclear with respect to the dbconfig directive. In fact, what I gather from the text is that if no DB_CONFIG file exists, any dbconfig directive will be used to generate one; otherwise, an existing DB_CONFIG file will not be altered. What is unclear is what happens if both a DB_CONFIG file and any dbconfig directives exist, and they differ? Who takes the precedence? What if any dbconfig directive is not present in the DB_CONFIG file?

I would say since dbconfig directives only work on a restart of slapd, and that if a DB_CONFIG is present, the DB_CONFIG should *always* take precedence. If dbconfig changes could make a difference via back-config, which they can't without a restart, then dbconfig stuff should override any DB_CONFIG.

Gavin,

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.