[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: config backend

At 11:43 PM 3/4/2003, Pierangelo Masarati wrote:
>It is very interesting; I think you already wrote about this
>some time ago, when talking about gentle restart or so.
>I believe this would become strikingly interesting if we could
>modify at least some of the settings while the server is running. 

In my opinion, slapd should never update a configuration file.
This is not to say that users should never be able to
dynamically update slapd's configuration.   If the configuration
is held in files, then to support dynamic updates, the server needs
to support re-reading of the files.   If the configuration
is held in the directory, then the server needs to support
update of the directory.   I would prefer the latter.

That is, why not have a backend which held configuration
information (maybe it would use flat files for storage, but
that's an implementation detail).  The default configuration
would be to support one listener, ldapi://, directory manager
set to the authorization identity associated with euid=0,egid=0
of the peer, no databases (other than the configuration), and
a simple ACL policy (access to * by rootdn write by * none).

To (re)configure the system, one just issues the appropriate
LDAP update operations....