[Pkg-openldap-devel] Proposal for the configuration in debian.

[Quanah Gibson-Mount]

--On Sunday, February 26, 2006 5:52 PM +0100 Matthijs Mohlmann 
<matthijs at cacholong.nl> wrote:


>>> - - /etc/ldap/schema/*
>>
>>
>>> The schema's that are needed to be included. This is already done.
>>
>>
>> Uh, this is a problem.  I have plenty of files in my /etc/ldap/schema/
>> directory which I do *not* expect to be included unconditionally in the
>> running slapd's config; I have alternate revisions of schema files that
>> I've tuned, I have conflicting schema files, and I even have an
>> /etc/ldap/schema/README file...  I don't think it's right to include all
>> of the schema files like this, I think it might be better to just
>> include the core schema files and possibly create an additional
>> /etc/ldap/slapd.d/ directory where packages can include config files
>> that would document additional schemas, etc.
>>
>> At that point, I expect the load order would be:
>>
>> include /etc/ldap/slapd.d/*.conf
>> include /etc/ldap/ldapdb/*.conf
>>
>> Note that the *.conf should give us a way of excluding old versions of
>> conffiles, à la run-parts.
>>
> Didn't thought about that, good suggestion.

Um, why are we creating a slapd.d directory?

"slapd.d" has special meaning in OpenLDAP 2.3: It is the directory that 
contains a cn=config backend.  We should not be creating *any* slapd.d 
directories unless we are moving wholesale to cn=config, which I do not 
recommend, since there are several overlays and backends that currently are 
not supported with cn=config.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITS/Shared Application Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html