>>>>> On Fri, 18 Nov 2005 16:57:04 +0000, Dave Shield <[EMAIL PROTECTED]> said:
Dave> Taking the Boolean table as an example, this says: Dave> The mteEventName of the event to invoke when Dave> mteTriggerType is 'boolean' and this trigger Dave> fires. A length of 0 indicates no event. The counter to that is the text for mteTriggerFalling that says: Notification that the falling threshold was met for triggers with mteTriggerType 'threshold'. It doesn't say "but only if they configured it to be sent". I don't think that arguing about this is worthwhile, as it's somewhat a stalemate. You're the developer of the recent code, so until I rewrite yours you win ;-) Dave> What if I deliberately don't *want* to issue a notification on a Dave> particular trigger firing? For example, I'm setting up a rising Dave> threshold monitor, and I'm not interested in the falling event Dave> (apart from re-arming the rising trigger). How could I Dave> configure that sort of behaviour if the implementation Dave> automatically forces a mteTriggerFalling notification? Sure - I Dave> could configure the trap receiver to ignore such notifications, Dave> but why should I have to waste my network bandwidth with stuff Dave> that I'm not interested in?! One not-a-real-word: snmpNotifyFilterTable. It even allows one receiver who does care to receive it and another not. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
