On Fri, 2010-03-12 at 17:33 -0800, Wes Hardaker wrote: > >>>>> 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.
Given that BER encodes the first two digits in one octet I suspect you can't do .1 either. > (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. Yes, but that is what I would expect in this case, and certainly in the . case. /MF ------------------------------------------------------------------------------ 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