https://net-snmp.sourceforge.io/wiki/index.php?action=history&feed=atom&title=Template%3AFAQ%3AAgent_12Template:FAQ:Agent 12 - Revision history2026-05-02T06:55:32ZRevision history for this page on the wikiMediaWiki 1.26.3https://net-snmp.sourceforge.io/wiki/index.php?title=Template:FAQ:Agent_12&diff=1656&oldid=prevDts12 at 19:51, 22 October 20062006-10-22T19:51:37Z<p></p>
<p><b>New page</b></p><div>With care.<br />
<br />
As mentioned in the earlier "thread-safe" FAQ entry, the Net-SNMP<br />
agent (including the AgentX subagent) has not been designed for<br />
threaded operation. In particular, it makes use of various global<br />
variables without attempting to protect them against simultaneous<br />
use. This means that it is '''NOT''' safe to have SNMP or AgentX<br />
related processing in two separate threads. This also applies to<br />
handling GET (and SET) processing in one thread, and generating traps<br />
in another. This is still vulnerable to the usual threading problems.<br />
<br />
However, as long as '''all''' of the SNMP-related activity is limited<br />
to the one thread, then there should be no reason why this cannot<br />
safely communicate with other threads within the same application,<br />
using private (thread-safe) mechanisms.<br />
<br />
But in terms of the Net-SNMP-provided code, the agent (and AgentX<br />
subagent) should '''not''' be regarded as thread-safe.</div>Dts12