Dave Shield wrote:
The current test suite is *much* better than it was, but I don't
think that the "snmpwalk" test is sufficiently focused to be very
useful.
I think it fills a gap that the more focused tests leave. It verifies
two very basic assumption:
1) a series of GETNEXT requests should never hang/crash the agent.
2) the returned type for any oid should match the type defined in the
MIBs we ship
If it fails on any particular system, where should we
start looking to try and fix the problem?
The directory /tmp/snmp-test-58-* will contain the complete logs of the
test procedure, including packet dumps and snmpwalk output.
You'll also have an easy test case to reproduce the problem and for
further investigation, e.g. under gdb.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
