On Monday 25 June 2007 16:30:28 Dave Shield wrote: > OK - can you please try the following: > > a) Replace the directive "exec truth /bin/true" > with "sh truth /tmp/true" > > b) Create a shell script /tmp/true > containing > > #!/bin/sh > exit 0 > > and re-test the agent. Does this also go runaway? > Then > > c) Edit the shell script /tmp/true to read > > #!/bin/sh > echo true > exit 0 > > and re-test the agent. What happens then? > > Dave
Unfortunately the same freeze happens with both, and it never gets to printing the stdout from the script. This is from when I executed c): # snmpwalk -On -v 2c -c public localhost .1.3.6.1.4.1.2021.8 .1.3.6.1.4.1.2021.8.1.1.1 = INTEGER: 1 .1.3.6.1.4.1.2021.8.1.2.1 = STRING: truth .1.3.6.1.4.1.2021.8.1.3.1 = STRING: /tmp/true .1.3.6.1.4.1.2021.8.1.100.1 = INTEGER: 0 Timeout: No Response from localhost Also, what's strange is how when I changed `exit 0` to `exit 1`, it printed ".1.3.6.1.4.1.2021.8.1.100.1 = INTEGER: 256". The same logic applied to `exit 2`, as it then printed "INTEGER: 512" for that OID. Juuso ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
