Pierangelo Masarati wrote:
There will not be any active operations when back-config is operating. Remember that on write operations it suspends the thread pool before it does anything else. As such, you can perform whatever cleanup is required, issuing ldap_unbind()s on all of the cached connections, without regard to locking or any other concerns, before returning from the config handler.I have back-ldap, the chain and the translucent overlays working fine
with table-driven parsing. I'm also able to bootstrap back-ldap from an
empty slapd.conf.
One issue is that (I guess) if we let the administrator change the URI of back-ldap, the cached connections should be invalidated... I'm afraid this will cause problems with those that are in use, since libldap calls in general don't like being passed a NULL ld.
-- -- Howard Chu Chief Architect, Symas Corp. Director, Highland Sun http://www.symas.com http://highlandsun.com/hyc Symas: Premier OpenSource Development and Support