denyop (Was: commit: ldap/servers/slapd/back-monitor back-monitor.h database.c init.c proto-back-monitor.h)

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

As I noted in denyops discussions, we should allow the
restrict op flags to be individually set.  That is,
'readonly on' should be complemented by:
        denyop modify
        denyop rename
        denyop delete
        denyop add

If we do that, then it seems odd to have readOnly boolean
in back-monitor.  Maybe we should have a multi-valued
attribute instead:
 denyop: modify
 denyop: compare
 denyop: 1.3.6.1.4.1.4203.1.11.1

(the last is food for thought)

Kurt


At 04:56 PM 4/26/2004, hyc@OpenLDAP.org wrote:
>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.
>
>
>CVS Web URLs:
>  http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-monitor/
>    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-monitor/back-monitor.h
>    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-monitor/database.c
>    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-monitor/init.c
>    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-monitor/proto-back-monitor.h
>
>Changes are generally available on cvs.openldap.org (and CVSweb)
>within 30 minutes of being committed.