>>>>> On Tue, 09 Mar 2010 20:00:00 +0100, Magnus Fromreide >>>>> <ma...@lysator.liu.se> said:
>> a) start at .1 >> pros: will show all available objects >> cons: will show all available objects MF> I think I prefer a slight variation on this one if it is chosen: MF> start at . as opposed to .1. I'm not sure you can do that. I'd actually have to go look through the SNMP and BER docs to figure out whether a zero-length OID is legal in both of them. (if you specify just . to our tools now you'll find that it'll actually do .1). Though snmpwalk could be smarter and start from .0 and do getnexts to infinity, but that's a different subject. >> c) print error and exit if no start point specified (suggest mib-2 or .1) >> pros: makes it very clear what's going on >> cons: big change in behavior This is actually my favorite personal option, but at the same time I don't think it should be chosen. -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
