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

Re: back-config again

I'd also like to note that this is just "food for thought" for
those actually doing the coding...


At 10:15 AM 4/4/2004, Kurt D. Zeilenga wrote:
>At 11:25 PM 4/3/2004, Hallvard B Furuseth wrote:
>>Kurt D. Zeilenga writes:
>>>At 11:21 PM 3/28/2004, Michael Ströder wrote:
>>>>Kurt D. Zeilenga wrote:
>>>>>Here are some thoughts on a possible bootstrapping scheme:
>>>>>Also note the use of ldapi:// and -Y EXTERNAL for the
>>>>>initial add.  The add would be allowed if the client's
>>>>>uid was same as server's uid.
>>>>And what would happen if one would like to build --without-cyrus-sasl?
>>> Builtin EXTERNAL (coming soon I hope) or slapadd(8).
>>So slapadd is not configured by the config backend?
>I was noting that slapadd could be used to configure the config
>backend (which then slapadd could make further use of).  That is,
>slapadd(8) would be sufficient for bootstrapping (including
>addition of databases).
>Beyond bootstrapping, using slapadd (and slapcat) to configure
>the system is limiting.  In particular, the slap tools do not
>provide any entry modification or deletion or renaming capability.
>But I'm not really thinking of using slap tools as a general
>configuration mechanism.  The general mechanism, I think, should
>be LDAP.
>One could provide more slap tools (e.g., slapmodify) to fill the
>But I'd actually like to go the other direction, make it
>possible (and where possible, more effective) to use LDAP-based
>mechanisms.  For instance, it should be possible to add indices
>on the fly (and to regenerate indices on the fly).  But this is
>a very long way off.