I installed net-snmp 5.4.0 (precompiled binaries) on a windows 2003 server sp1.
In the configuration of snmpd I defined the following
pass .1.3.6.1.4.1.24704.3.1.1.1.1 cmd /c /programme/net-snmp/jobs/test.bat
you may use also pass .1.3.6.1.4.1.24704.3.1.1.1.1 /programme/net-snmp/jobs/test.bat
it makes no difference.
The content of test.bat is
@ECHO OFF
ECHO %2.0
ECHO gauge
ECHO 1
The content of the batch is just a placebo to demonstrate the problem. In reality a script is started which evaluates the oid and delivers the appropriate data.
An opennms installation uses the local snmpd agent.
Every time the snmpd agent is called by the opennms station the batch test.bat is started and delivers the data. This works without any problems.
The problem is that the process and the threads created by snmpd are not closed. This night the server had a loss of 70 MB of RAM which are freed by a restart of the the snmpd service.
If you download proc explorer from www.sysinternals.com and select the snmpd process you can see in the lower pane the growing number of unclosed processes and threads.
Logged In: YES
user_id=85836
Originator: NO
Thanks for the bug report! We've fixed the problem in the 5.4.x code branch and the main development tree, so it should be fixed in future releases of the net-snmp package.