[Date Prev][Date Next]
Issue with custom schema extensions for back-monitor
- To: openldap-devel@OpenLDAP.org
- Subject: Issue with custom schema extensions for back-monitor
- From: "Pierangelo Masarati" <email@example.com>
- Date: Thu, 28 Apr 2005 10:32:52 +0200 (CEST)
- Importance: Normal
- User-agent: SquirrelMail/1.4.3a-1
I'm facing an issue in allowing modules to customize back-monitor when
they need to derive schema items from those of back-monitor.
Background: back-monitor defines schema items from builtin tables; this
occurs in monitor_back_db_init(), which is called when "database monitor"
occurs in slapd.conf.
Scenario: consider the case of an overlay "foobar" that appends data to
existing monitor entries, for specific monitoring needs, and it needs to
define own schema items. For clarity and consistency, it is advisable
that specific items be derived from monitor generic schema items, like the
"monitorObject" for objectClasses, "monitoredInfo", "monitorCounter",
"monitorTimestamp" for attribute types.
As such, this declaration must occur not earlier than in
foobar_over_db_init, because this is called when "overlay foobar" occurs
in slapd-conf, provided "database monitor" appears before "overlay
The issue is mainly in defining specific access rules to those items; in
fact, if "overlay foobar" occurs in a database defined after "database
monitor", those rules must be within the "database monitor" block, but
they cannot use specific schema items that will be defined later.
My question is: does anybody see drawbacks in moving monitor schema
definition in monitor_back_initialize(), so that specific schema
definitions can be moved in foobar_over_initialize() and the only care
must be in loading the back-monitor.la and the foobar.la modules in the
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497