H_UP notification regarless scheduled downtime

Andreas Ericsson ae at op5.se
Tue Nov 6 19:20:24 CET 2012


On 11/06/2012 05:07 PM, Ricardo Jose Maraschini wrote:
> Hya!
> 
> * Andreas Ericsson (ae at op5.se) wrote:
>> It's expected behaviour if you got the problem notification that
>> preceded the recovery notification. Otherwise it's not.
> 
> That's ok, but the same behaviour apparently isn't valid for service
> notifications. BTW, the following code sounds kinda strange and
> senseless to me. Is there any possibility to get first_problem_time !=
> of svc->last_time_ok on it ?
> 
> As it's running ok so far, i just cut it off, but maybe i should only
> remove those svc->last_time_xxx > svc->last_time_ok during comparsions.
> 

It looks as if that should be impossible, but I've had a few beers right
now and I'm leaving for a one-week vacation in egypt in ten hours, so
I'll have to postpone a further analysis of this patch and its ultimate
consequences.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d




More information about the Developers mailing list