Hi,
Not clear, how the remove_trap_session() function is invoked in the case of
regular snmpd(non agentx config)? It has a free_trap_session() commented out
quoting an agentx scenario.
But I think, this can cause an issue in non agentx environment, when an
existing trapsink/trap2sink is removed and a new trapsink added and snmpd given
a SIGHUP during a reconfig() invocation, this has the potential of sending
traps to both the sessions(extra unwanted traps for the earlier sessions and as
well as traps to new session) as it remembers earlier session.
Any insight/tips about this, will be appreciated.
Thanks
---------------------------------
Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. -------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
