RE: commit: ldap/servers/slapd/back-monitor back-monitor.h database.c init.c proto-back-monitor.h

["Pierangelo Masarati" <ando@sys-net.it>]

>> -----Original Message-----
>> From: Pierangelo Masarati [mailto:ando@sys-net.it]
>
>> > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/back-monitor
>> >
>> > Modified Files:
>> > 	back-monitor.h  1.31 -> 1.32
>> > 	database.c  1.40 -> 1.41
>> > 	init.c  1.70 -> 1.71
>> > 	proto-back-monitor.h  1.16 -> 1.17
>> >
>> > Log Message:
>> > Added readOnly attribute, can be toggled on individual databases.
>>
>> Howard,
>>
>> this change is very interesting since it opens many new scenarios even
>> before back-config is available.  I wonder why you don't
>> allow editing of
>> readOnly for the entire server as well; is there a specific
>> reason, or you think it's not important?
>
> A much simpler reason - if you set the Global readOnly flag, there is no
> possible way to reset it, because all subsequent LDAPModify requests
> will be rejected.

We could solve the chicken-and-egg problem by allowing this type
of modify to rootdn only; of course it has to be rootdn of the
server, not of a specific backend.  I'm more and more in favor
of having a global BackendDB structure that holds global data,
making all global operations mimic those of a regular backend.

p.

-- 
Pierangelo Masarati
mailto:pierangelo.masarati@sys-net.it