In order to fix the problem where an inform session fails to open at startup, I'm integrating a patch (submitted a few years ago) to delay the engineID probe until it is needed.
The question is, what should the default behaviour be? Always delay the probe (any time snmp_open is called for a v3 session), or just delay for inform session? Of course a flag will be added to allow users to specify the non-default behaviour. The other option would be to allow a failed probe to successfully return, and set up to retry the probe when needed. -- 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. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
