On Wed, 23 Jun 2004, David Nolan wrote:
> Actually with Mon 0.99.* and the 1.0.pre* code you *WILL* get alerts if you
> get traps while the scheduler is stopped. This is one of the bugs that are
> fixed in my code, i.e. in the CVS HEAD on sourceforge, soon to be released
> as Mon 1.1.*.
ok well whether or not it's a bug may be debatable (traps aren't scheduled
so stopping the scheduler shouldn't affect them), but it sounds like the
behavior of your version may be more intuitive. maybe not. i don't know.
there seem to be a number of nuances here, and i originally intended
"moncmd stop" to control these first two:
related to scheduling loop:
-stopping monitors from being scheduled thus stopping the
possibility of alerts from them
-stopping trap timeout alerts
not related to the scheduling loop:
-stopping alerts from traps
-delaying/stopping the processing of inbound traps
thoughts about the other two, or maybe more?
_______________________________________________
mon mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/mon
