Hi,
According to the 5.3.0.1 implementation, the engine ID discovery
is being done synchronously. Since the discovery is using the function
snmp_sess_synch_response passing as argument the session that wants to
be created, the agent is blocked during the discovery process not
allowing to receive requests from any other sessions (like port 161).
Did someone try to modify the code to do engineID discovery
asynchronously? Is there a some reason why the discovery is being done
synchronously?

Thanks in advance,

Pablo

-------------------------------------------------------------------------
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
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders