Mike Jackson wrote:
This function exists in OpenLDAP 2.3. You can perform all of the server administration and configuration via LDAP; you can add any definitions via LDAP without requiring a server restart. In particular, for schema, you can collect related schema together into a single LDAP entry and propagate/replicate it to any other server; there is no need to dump it all into a catch-all file. You can add plugins/dynamic modules on the fly, without requiring a restart for them to take effect. (However, to remove a plugin will require a restart to reclaim its memory.) In back-bdb you can edit the indexing configuration on the fly as well; there's no need to stop, run slapindex, and restart.Sorry, I mistakenly replied only to Kurt...
----- Forwarded message from Mike Jackson <mj@sci.fi> -----
From: Mike Jackson <mj@sci.fi> To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> Date: Wed, 11 May 2005 00:55:40 +0300 Subject: Re: Obtain Schema files from a software client
Kurt D. Zeilenga (Kurt@OpenLDAP.org) wrote:
OpenLDAP 2.2 provides no mechanism for a client to obtain
the name of the schema file, clients should instead use the
general schema retrevial mechanism.
Kurt, Do you think it would make sense to implement a mechanism to replicate schema files and have the server automatically load them upon reciept?
Consider a network where there are 50 or more LDAP servers; adding a new schema file and restarting the servers is a major task. And adding schema into a catch-all file is not a good solution; it makes maintenance next to impossible...
-- -- Howard Chu Chief Architect, Symas Corp. Director, Highland Sun http://www.symas.com http://highlandsun.com/hyc Symas: Premier OpenSource Development and Support