On Wed, 13 Jul 2005, Gerardo Arceri wrote:
Hi, I use m4 and mon -M option to make it process the config files with said
m4, i use it to separate the diferent parts of the monitoring into diferent
files and using include() to join them into the main config. I usually sent
alerts to 4 or 5 guys
Yes, I'm aware of how dep_behavior works. I don't think it has much
bearing here, though, seeing as how the dependencies get evaluated
either way, and, either way, it's going to evaluate to "infinite
loop"...right? I could be wrong, but that's how I see it...
Can anyone give an example of a depe
Hi, I use m4 and mon -M
option to make it process the config files with said m4, i use it to
separate the diferent parts of the monitoring into diferent files and
using include() to join them into the main config. I usually sent
alerts to 4 or 5 guys and i need to repeat the alert and upalert
s
For the dependencies I’ve always
setup the dep_behavior switch as well to tell mon what should and how a dependency
is understood.
Here’s a clip from the man page
describing how it works.
dep_behavior {a|m}
The evaluation of dependency graphs can control the
suppression of eith
