Hello!
Is it a stupid idea to make snmpset able to et values of type NULL?
If it is then I think we should return the 'n' type list in snmpset.
If it isn't then I think we should add support for the 'n' type. It
boils down to the attached patch since most of the support is there
already.
/MF
Index: apps/snmpset.c
===================================================================
--- apps/snmpset.c (revision 16765)
+++ apps/snmpset.c (working copy)
@@ -83,7 +83,7 @@
fprintf(stderr, "\t\t\t q: don't print results on success\n");
fprintf(stderr, "\n TYPE: one of i, u, t, a, o, s, x, d, b, n\n");
fprintf(stderr,
- "\ti: INTEGER, u: unsigned INTEGER, t: TIMETICKS, a: IPADDRESS\n");
+ "\ti: INTEGER, u: unsigned INTEGER, t: TIMETICKS, a: IPADDRESS, n:NULL\n");
fprintf(stderr,
"\to: OBJID, s: STRING, x: HEX STRING, d: DECIMAL STRING, b: BITS\n");
#ifdef NETSNMP_WITH_OPAQUE_SPECIAL_TYPES
@@ -183,6 +183,7 @@
case 'x':
case 'd':
case 'b':
+ case 'n':
#ifdef NETSNMP_WITH_OPAQUE_SPECIAL_TYPES
case 'I':
case 'U':
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
