Is the Net-SNMP library designed in a way to "survive" a restart cycle of snmpd daemon?
I am facing a problem when my AgentX subagent stops sending traps after the snmpd daemon has been restarted. The subagent is a part of other program (log server) so it is not desirable for it to require a restart each time the snmpd is restarted. I'm using the snmp_select_info (+snmp_read/snmp_timeout) in the main loop of my program to handle activity on SNMP sockets together with my own sockets and it works well. Each time I call send_v2trap to generate a trap, one SNMP socket is selected (it receives some kind of confirmation, probably). When I restart the snmpd, again one SNMP socket is selected, but then the following snmp_select_info returns a value that is by one less then previously - thus one socket must have been closed and forgotten and this is probably the most important one (for communication with master agent) because no further send_v2trap is confirmed (and some SNMP socket selected) nor any trap is delivered to registered trapsinks. Do any of you know about this problem and its possible solution? Thank you, Paul ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
