Is there a way to turn off dynamic config support in 2.3.X? After looking at the Admin Guide, man pages, mailing lists, and the FAQ-O-Matic I've failed to figure out how to do it; is it possible?
I was expecting to find something like --enable-dynamic-config=no or maybe a slapd option.
Thanks,
-- Ian Tegebo
Ian A. Tegebo wrote:
Is there a way to turn off dynamic config support in 2.3.X? After looking at the Admin Guide, man pages, mailing lists, and the FAQ-O-Matic I've failed to figure out how to do it; is it possible?
I was expecting to find something like --enable-dynamic-config=no or maybe a slapd option.
Dynamic configuration is now bundled into slapd (and slaptools, of course); however, if you don't instruct it to create a permanent config database and use it (namely via -F option), you can keep using slapd.conf seamlessly. Moreover, if you don't provide an entry point to dynamic configuration, by not explicitating the "database config", no dynamic configuration can occur via protocol. Is this enough?
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati@sys-net.it ------------------------------------------
On Thu, Oct 26, 2006 at 12:28:17AM +0200, Pierangelo Masarati wrote:
Ian A. Tegebo wrote:
Is there a way to turn off dynamic config support in 2.3.X? After looking at the Admin Guide, man pages, mailing lists, and the FAQ-O-Matic I've failed to figure out how to do it; is it possible?
I was expecting to find something like --enable-dynamic-config=no or maybe a slapd option.
Dynamic configuration is now bundled into slapd (and slaptools, of course); however, if you don't instruct it to create a permanent config database and use it (namely via -F option), you can keep using slapd.conf seamlessly. Moreover, if you don't provide an entry point to dynamic configuration, by not explicitating the "database config", no dynamic configuration can occur via protocol. Is this enough?
Thanks for the reply. I'm afraid I'm still confused. I wasn't sure what you meant by "using slapd.conf seamlessly"; do you mean that by not specifying the -F option I would be using "static configuration"?
My initial setup wasn't using -F and I was still getting a warning about my backend not supporting dynamic config. Next I did specify a directory for -F as well as a config file with -f as per the man page for slapd. This created files as expected for my BDB backend but it still gave me the same error for my java backend. This resulted in slapd not starting.
So I think I'm confused because with and without -F I'm still getting a warning in my debug output as well as a non-starting slapd.
Thanks for your time,
-- Ian Tegebo
Ian A. Tegebo wrote:
Thanks for the reply. I'm afraid I'm still confused. I wasn't sure what you meant by "using slapd.conf seamlessly"; do you mean that by not specifying the -F option I would be using "static configuration"?
My initial setup wasn't using -F and I was still getting a warning about my backend not supporting dynamic config. Next I did specify a directory for -F as well as a config file with -f as per the man page for slapd. This created files as expected for my BDB backend but it still gave me the same error for my java backend. This resulted in slapd not starting.
So I think I'm confused because with and without -F I'm still getting a warning in my debug output as well as a non-starting slapd.
Thanks for your time,
If you're not using dynamic config, then you should just use slapd.conf as always and ignore the warning. I.e., the warning is irrelevant if you never use dynamic configuration on that backend.
--On Wednesday, October 25, 2006 6:51 PM -0700 Howard Chu hyc@symas.com wrote:
If you're not using dynamic config, then you should just use slapd.conf as always and ignore the warning. I.e., the warning is irrelevant if you never use dynamic configuration on that backend.
Or basically, see it as a warning that you cannot and should not use the dynamic config backend for your configuration. Which means you should stick to the use of slapd.conf.
--Quanah
-- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
Howard Chu wrote:
Ian A. Tegebo wrote:
So I think I'm confused because with and without -F I'm still getting a warning in my debug output as well as a non-starting slapd.
If you're not using dynamic config, then you should just use slapd.conf as always and ignore the warning. I.e., the warning is irrelevant if you never use dynamic configuration on that backend.
Or, add support for dynamic config to your backend (for example, coding by example from existing backends and overlays; right now there are examples covering possibly any need in terms of types of functionalities, up to dynamic re-indexing). The bare bone would be to allow configuration only at startup, disabling run-time changes.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati@sys-net.it ------------------------------------------
openldap-software@openldap.org