-----BEGIN PGP SIGNED MESSAGE-----
I'm looking over back-monitor's interface to get some more monitoring to
back-ldap, mainly operation count, just like the one in
cn=operations,cn=monitor and finishing the connection monitoring in
There is a part of the monitor API that is a bit unclear to me:
In order to register an entry with register_entry(), one needs a
monitor_subsys_t structure, but how to obtain one? Is it a
back-monitor's job to appoint one or the monitored backend's?
The only use of this structure outside back-monitor is back-ldap again,
not relying on anyone when populating the structure, however a comment
directly above that code reads: "set up the fake subsystem [...]", where
the "fake" reads to me as "we shouldn't need one at all".
I understand the monitoring in back-ldap is functionally a stub with the
infrastructure *mostly* done, so maybe there was a rewrite of the
relevant code planned? What else should I take into consideration and/or
be looking into during my efforts?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.