Bug in mon?

To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Bug in mon?
From: "Ted Pavlic" <tpavlic@xxxxxxxxxxx>
Date: Thu, 29 Jun 2000 12:34:11 -0400
I believe the latest version of mon is 0.38.18, right?

Whenever I define a startup alert, it never passes the -u to the alert to
tell it it is an upalert. Consequently, all of my startupalerts actually are
startalerts :(.

Looking through mon, I see that in the section which execs the alerts, he
only checks to see if FL_UPALERT is on and not FL_STARTUPALERT.

By changing it so that both flags are checked, my startupalerts started

Another change I could have done was change this section:


to be:

$FL_STARTUPALERT=18; # 2 & 16

Has anyone else had this problem with mon? A *LONG* time ago I used mon for
my LVS and it worked fine... I forget what version that is. I was using it
now for a new cluster I'm building and having the trouble.

All the best --

<Prev in Thread] Current Thread [Next in Thread>