> NEBERROR_CALLBACKCANCEL is used as a one-time measure to cancel
> checks, while NEBERROR_CALLBACKOVERRIDE is used to cancel them
> without rescheduling them. I'm not sure if we want to muddy the
> distinctions by having them mean the same for things that aren't
> re-scheduled automagically.
>
Thanks for your comments.
I believed that the macro use was more obvious than the rescheduling
issue. I thaught that it was a way for modules to say "ok I'll do it
myself" (OVERRIDE) or "no one should do it" (CANCEL), as per the
comments in neberrors.h :
#define NEBERROR_CALLBACKOVERRIDE 206 /* module wants to
override default Nagios handling of event */
#define NEBERROR_CALLBACKCANCEL 207 /* module wants to cancel
callbacks to other modules */
And thus the fact that for checks, module has to care about
rescheduling is just implicit when using NEBERROR_CALLBACKOVERRIDE.
For event-handlers I think that the same logic holds, either the
module want to execute the event-handler itself or just cancel its
execution.
Best regards,
--=20
Matthieu KERMAGORET | D=C3=A9veloppeur
[email protected]
MERETHIS est =C3=A9diteur du logiciel Centreon.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]