On Wed, 15 Jun 2005 08:24:29 -0700 (PDT) Surya wrote:
SP> What kind of problems? Could you please elaborate or
SP> point to?
Sure. The net-snmp libraries have not been made thread safe, with the exception
of the snmp_session client APIs. None of the agent code has even been evaluated
for thread-safety. There are definitely global variable, and they are not
protected by any type of locks.
SP> I could receive messages and send traps from
SP> the new thread. I don't share data in my code.
SP> Probably the send_easy_traps or other Trap APIs might
SP> share data. I haven't looked in detail yet as I didn't
SP> notice any 'major' problems.
Interactions between threads can be subtle and based on timing. I would
strongly recommend that you not do this in any production environment. It's
just a matter of time before problems occur. Search the archives, and you will
find reports of people trying this and running into serious issues.
In summary, using snmp in multiple threads in the agent IS COMPLETELY
UNSUPPORTED.
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
unless they are requests for paid consulting services.
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
