On Sun, Aug 19, 2001 at 12:33:41PM -0700, Jim Trocki wrote:
> ******DEFAULT BEHAVIOR HAS CHANGED FOR THE FOLLOWING FEATURES************
>
> the following two defaults were changed, since they seem to be unintuitive
> to most people, based on feedback given on the mailing list.
>
> -the default is now the old "summary" behavior for alertafter. that
> means that for successive failures with "alertafter" used to suppress
> multiple alerts, only the summary line will be used to short-circuit
> the alert suppression. to get the old behavior, append "no_summary"
> to the alertafter line. the old "summary" syntax is still permitted
> to help w/backwards compatibility.
I've been trying to update to 0.99.1 and have become very confused by this
statement. The first thing is that "alertafter" doesn't have a "summary"
option, it's "alertevery XX summary". So I went through and reversed my
alertevery statements ("alertevery XX summary" becomes "alertevery XX" and
"alertevery XX" becomes "alertevery XX no_summary"). When I try to start
mon, I get the following error:
Aug 22 11:37:27 crystal mon[20348]: cf error: invalid time interval ''
(syntax: alertevery {positive number}{smhd}), line 101
Line 101 in the config is:
alertevery 3h no_summary
So I started digging around in the mon code and can't find "no_summary"
anywhere in the code. I did find a chunk around line 1271 though:
#
# for backawards-compatibility with <= 0.38.21
#
elsif ($args =~ /(\S+) \s+ summary/ix)
{
$args = $1;
}
This is in the alertevery handler. More poking around found the
"observe_detail" parameter instead of "no_summary".
After changing the "no_summary" commands to "observe_detail", mon starts up.
--
Randomly Generated Tagline:
"I have the vision, and I'd like to share it with you before the peyote
wears off." - Bill Maher
