On Fri, 07 Oct 2005 15:28:06 +0100 Dave wrote: DS> One other question has come to light: DS> When the current implementation sets up a "monitor" directive, DS> it doesn't appear to run the test immediately - even if the test DS> does actually hold true. Instead, it waits until the monitor DS> frequency has expired, and *then* sends the trap.
I've had reports/complaints about this in irc, and have meant to fix it. DS> The new implementation takes proper notes of this flag, so would DS> generate the trap immediately. Should I retain the same visible DS> behaviour as the current code (i.e. have "monitor" default to DS> mteTriggerBooleanStartup = false), or keep the same MIB settings DS> as the current code (and have the behaviour change) ? No, fix it. People want to know why they can snmpget and error condition immediately, but don't get a trap... -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
