On 16 April 2012 21:18, Norman Rädke <normanrae...@gmx.de> wrote:
> I using the NET-SNMP version 5.6.1.
Hmmm....
It might be worth trying with the upcoming 5.6.2 release
(or with v5.7.1). I've had a quick look through the ChangeLog,
and there are various commits that refer to close() handling.
Nothing that screams out to be clearly relevant to your problem,
but it's worth checking to see.
> The error was logged by the threaded application
The other suggestion I'd make would be to avoid the problem
altogether by re-using the same session structure (and socket)
each time the routine is called.
Something like:
static snmp_session *ss = NULL;
if ( ss == NULL ) {
snmp_session session;
init_snmp("libpbmoninsp_trap");
:
ss = snmp_add(....);
}
and then omit the termination block:
snmp_close(ss);
snmp_shutdown("libpbmoninsp_trap");
SOCK_CLEANUP;
That way you'd only have one session open all the time,
and wouldn't need a separate socket for each call.
Dave
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
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
