Allow event-handler cancelation

[Matthieu Kermagoret]

On Tue, Mar 8, 2011 at 10:29 AM, Andreas Ericsson <ae at op5.se> wrote:
> 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,

-- 
Matthieu KERMAGORET | Développeur

mkermagoret at merethis.com

MERETHIS est éditeur du logiciel Centreon.

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Nagios-devel mailing list
Nagios-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-devel