[ net-snmp-Bugs-2899063 ] Old mteTriggers not deleted on SIGHUP

[SourceForge.net <no...@so...>]

Bugs item #2899063, was opened at 2009-11-17 13:20
Message generated for change (Tracker Item Submitted) made by farnerup
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=2899063&group_id=12694

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: agent
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Fredrik Arnerup (farnerup)
Assigned to: Nobody/Anonymous (nobody)
Summary: Old mteTriggers not deleted on SIGHUP

Initial Comment:
We have two "monitor" statements in snmpd.conf. I put a printf in
mteTrigger_enable() to see how many times it is called.
At startup it is called twice (once for each monitor statement). Upon the first SIGHUP it is called four times, upon the second, six times, and so on.

We run a lot of automated tests that send SIGHUP to snmpd many times, and it seems that eventually snmpd has registered so many timers that the whole machine is doing little else but handling monitor timers.

This problem might be related to this:
http://aspn.activestate.com/ASPN/Mail/Message/net-smtp-users/3350806

We are using Net-SNMP 5.4.2 on linux ppc.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=2899063&group_id=12694