Since we're on the topic of that _trap_timer thingie...
Upon launch or reset of mon, each trap's _trap_timer is set to the value of its traptimeout. After that, _trap_timer keeps getting decremented as time progresses. This seems to make sense.
But, as I read the code, it's impossible for an alert to be sent about a trap timeout unless _trap_timer has reached 0.
So let's say I have a trap whose timeout is 1 month. I can't get alerted about this trap until at least 1 month has passed since the most recent launch or reset of 'mon', right? So does that mean the only way I'll ever know about a timeout of that trap is if I manage to go a month without relaunching or resetting mon?
Tim
_______________________________________________ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
