And/Or Logic and Event Handlers

[Jamie Baddeley]

isn't that what check_cluster does?

anyways I think I've got a cunning plan to stick a tail onto.

Thanks for the thoughts Stanley.

Cheers

Jamie
----- Original Message ----- 
From: "Stanley Hopcroft" <Stanley.Hopcroft at IPAustralia.Gov.AU>
To: <nagios-users at lists.sourceforge.net>
Cc: "Jamie Baddeley" <jamie.baddeley at vpc.co.nz>
Sent: Monday, May 05, 2003 11:36 AM
Subject: Re: [Nagios-users] And/Or Logic and Event Handlers


> And a few corrections,
> 
> On Sun, May 04, 2003 at 09:24:33PM +1000, Stanley Hopcroft wrote:
> > 
> > 2 Have your event handler keep state (eg here a global event handler
> > updates an mySQL database for PHB reporting needs [using the Win OBDC
> > drivers so they can import into MS spreadsheets etc] and respond to a B
> > down by checking if A is already down.
> > 
> 
> there is no need to keep state since Nag already does for you in 
> status.log. Simply have your event handler check the state of A and B 
> recorded there.
> 
> Yours sincerely.
> 
> 
> -- 
> ------------------------------------------------------------------------
> Stanley Hopcroft
> ------------------------------------------------------------------------
> 
> '...No man is an island, entire of itself; every man is a piece of the
> continent, a part of the main. If a clod be washed away by the sea,
> Europe is the less, as well as if a promontory were, as well as if a
> manor of thy friend's or of thine own were. Any man's death diminishes
> me, because I am involved in mankind; and therefore never send to know
> for whom the bell tolls; it tolls for thee...'
> 
> from Meditation 17, J Donne.
> 



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null