I started using the netsnmp python module that is bundled with NET-SNM
5.4.1and I've encountered some inconveniences while using it:
1. Handling of any errors is very poor. I could not determine any
difference between a request that failed due to timeout or due to an error
response from the server, and in the case of an error returned from the
server there's no indication of what the error was. One especially bad
example of poor error handling is that if the netsnmp.snmpwalk function
encounters an error (for example, a timeout) after successfully performing a
number of GetNext requests, it will return a partial result with no
indication that an error happened.
2. Messages are printed to stdout or stderr. I expect that a library like
the netsnmp python module will communicate with the calling code by
returning data and possibly raising exceptions when I call the functions,
not by printing messages.
Is there any work planned to fix either of these problems? If not, if I
were to modify the library to throw exceptions from the snmpget, snmpwalk,
etc, functions when they encountered errors and submit a patch, would the
NET-SNMP developers have any objection in principle to that type of change?
Nathan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
