On Thu, 20 Apr 2006, Howard Chu wrote:
Regardless of any existing config directory, when both flags are
specified, the slapd.conf file is read and written out in config
directory format. If there were any other conditions on the behavior, it
would say so. Since there is not, it does not.
With
Eric Irrgang wrote:
On Thu, 20 Apr 2006, Howard Chu wrote:
Regardless of any existing config directory, when both flags are
specified, the slapd.conf file is read and written out in config
directory format. If there were any other conditions on the behavior, it
would say so. Since there is
Okay... Maybe I should be asking instead what you consider best practice
for maintaining a configuration with OL2.3. At this point it sounds like
every change to slapd.conf warrants removal of both slapd.d and DB_CONFIG.
That's fine, if maintaining configuration in slapd.conf is the way to go,
Howard Chu wrote:
Eric Irrgang wrote:
I'm also a little confused by the intended behavior of include files.
slapd.conf include directives are only preserved in the config directory
for purposes of documentation, they are never reprocessed.
This is indeed confusing. I'd rather drop this.
Michael Ströder wrote:
Howard Chu wrote:
Eric Irrgang wrote:
I'm also a little confused by the intended behavior of include files.
slapd.conf include directives are only preserved in the config directory
for purposes of documentation, they are never reprocessed.
This is indeed confusing.
