[Date Prev][Date Next]
Re: (ITS#6016) Make moduleload automatic
> firstname.lastname@example.org wrote:
>> Full_Name: Andrew Bartlett
>> Version: 2.4.15
>> OS: Fedora 9
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (220.127.116.11)
>> In Samba4, we generate a slapd.conf for OpenLDAP as part of our
>> provision-backend process. This avoids administrators needing to guess at
>> Samba's specific requirements.
>> However, this places the Samba4 software in the position of having to guess how
>> this host's OpenLDAP installation was compiled. In particular, we need to guess
>> if the required overlays are built in, or modules.
>> Work was done a while back to avoid us having to guess what the module path is
>> (the default is is now hard-coded in the binary), but we still have to guess
>> which set of modules to load. Currently this is done in 'make test' by guessing
>> different sets of modules in an included 'modules.conf' and running slaptest
>> until we find a combination that works.
>> We (Samba4) would really like it if the slapd binary would load modules
>> (assuming a one-to-one mapping between overlay/backend names and modules) from
>> that default path, if not found static in the binary.
>> This way, Samba would not specify modules at all in the slapd.conf, but they
>> would be loaded as required, if required.
>> Andrew Bartlett
>> (As discussed with Howard Chu on #openldap-devel)
> As a further clarification - we're only considering this for backends and
> overlays; other dynamically loaded elements' (like syntaxes, password hashes,
> whatever) behavior will not be changed.
I see quite a few issues (unless already discussed). For example, one
would typically discover the need to load back_monitor.la only close to
the end of the configuration, while the module defines some specific
schema and even some specific calls that may be needed by other backends
instantiated earlier in order to allow custom monitoring. I guess the
problem can be generalized.
> And before we go there, what if we just provided a slapd option to dump out
> all of its compiled-in paths? Then you could inspect the modulepath and see
> whether any modules of interest reside there. ?
Ing. Pierangelo Masarati
OpenLDAP Core Team
via Dossi, 8 - 27100 Pavia - ITALIA
Office: +39 02 23998309
Mobile: +39 333 4963172
Fax: +39 0382 476497