- in case we appended an entry to a yet unknown parent, we don't know
the full DN, so unregistering needs to be possible based on the
available data;
- complete unregister calls so that not-yet-registered stuff can be
removed from limbo
database entry in cn=monitor
- improve support for custom attribute/callback registration
in back-monitor
- design API for registered antry/attr/callback removal in back-monitor
HEADS UP: now back-bdb requires back-monitor to be present, either static
or dynamically loaded __before__ back-bdb/back-hdb is initialized.
This works for sure if both back-bdb & back-monitor are static or dynamic
(provided back-monitor.la is loaded before back_bdb.la); it is not clear
what happens if back-bdb is static and back-monitor is dynamic. In case,
either make back-bdb monitoring conditional, or hardwire back-monitor
much like back-config and back-ldif.
The old monitoring stuff has been removed; the new backend is
enabled by using --enable-monitor at configure time and requires
database monitor
in slapd.conf to be activated. At present it implements a subset
of the old monitoring options, and it should be extendable to
a number of different subsystems. The search operation has been
implementd; it does not honor abandon or size/time limits, though.
The compare and the abandon operations are planned.
Copyright Pierangelo Masarati <ando@sys-net.it>; the code is provided
AS IS with NO GUARANTEE. It can be used and distributed under the
conditions stated by the OpenLDAP Public License.
