-Coders,
upon receiving SIGHUP, snmptrapd rereads its configuration file(s) which can be quite useful.
However, version 5.1.2 effectively duplicates the traphandler registrations on every SIGHUP! I.e. after sending SIGHUP n times, a single trap triggers the corresponding traphandler n times! A show-stopper for anyone using snmptrapd and SIGHUP. :( Using "traphandle default" vs. "traphandle <oid>" doesn't make a difference.
Downgrading to 5.0.9 fixes this. I don't have 5.2/MAIN at hand to verify there.
Can someone please have a look at this?
+Thomas
-- Thomas Anders <[EMAIL PROTECTED]>
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
