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

Re: back-config design considerarions - Admin Guide fodder

--On Thursday, July 28, 2005 8:07 PM +0200 Michael StrÃder <michael@stroeder.com> wrote:

Quanah, I do see all the advantages of slapd.conf mentioned above. But I
also see the issues with inconsistencies and user confusion. Arent' you
then questioning usefulness of back-config in general?

No, not at all. I already intend to use it on my production systems. However, for doing a wide range of testing where I can make immediate changes and restart the server with a new version of slapd.conf, no, I don't intend to use it.

BTW: Testing various setups by using -F with different directories is as
easy as using -f. And you can check in the configdir/ tree to CVS as
well without problem.

Not really. I can copy slapd.conf and make minor tweaks to it very quickly, and store those slapd.conf files with specific tests quite easily.

Furthermore if in the future ACLs and access/audit logging is
implemented for back-config you have a much more powerful instrument to
track configuration changes than CVS for slapd.conf.

Last I checked, back-config supported my ACLs...

=> One has to decide which route to go and after that one has to follow
that route consequently to avoid inconsistencies and double effort.

And sometimes, there is more than one route to a destination, each route with its pros and cons.


Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

"These censorship operations against schools and libraries are stronger
than ever in the present religio-political climate. They often focus on
fantasy and sf books, which foster that deadly enemy to bigotry and blind
faith, the imagination." -- Ursula K. Le Guin