--On Tuesday, March 18, 2003 9:10 PM +0100 Mark Lawrence <[EMAIL PROTECTED]> wrote:

Unfortunately I'm not a perl guru. Can anyone confirm this behaviour
and/or send a patch?


Yes, that is the behavior. I'm unclear on whether or not it was the intended behavior, but I definitely agree with you that it is confusing. I submitted a patch for this some time ago, as part of a large patch set that I sent. It's a one line patch, so I'm including it below, with context since my line numbers will be different from the released version.

Unfortunately Jim hasn't had time to release a new Mon anytime recently. Maybe its time for us to start prodding him. I've got another large patch set to submit, including some significant bug fixes, and some new features, but I've been sitting on it till I could reconcile it with Jim's next release.


-David Nolan Network Software Developer Computing Services Carnegie Mellon University


diff -c -r1.7 -r1.6
*** mon 12 Aug 2002 21:14:48 -0000 1.7
--- mon 12 Aug 2002 20:42:49 -0000 1.6
***************
*** 2913,2919 ****
($tmnow - $sref->{"_first_failure"}
>= $sref->{"upalertafter"})))
{
! do_alert ($group, $service, $ibufs{$runningpid{$p}}, 0, $FL_UPALERT);
}


$sref->{"_ack"} = 0;
--- 2913,2919 ----
($tmnow - $sref->{"_first_failure"}
>= $sref->{"upalertafter"})))
{
! do_alert ($group, $service, $sref->{"_last_output"}, 0, $FL_UPALERT);
}


$sref->{"_ack"} = 0;

_______________________________________________
mon mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/mon

Reply via email to