On Tue, 2010-03-09 at 09:35 -0500, Robert Story wrote: > There was some discussion in the IRC channel this morning about the default > behavior of snmpwalk biting newbies. They will often run snmpwalk without > specifying a starting point, and by default snmpwalk will start the walk on > the mib-2 branch. This leaves users puzzled as to why they aren't getting > enterprise MIB objects. > > There were a few proposals for a possible fix: > > a) start at .1 > pros: will show all available objects > cons: will show all available objects
I think I prefer a slight variation on this one if it is chosen: start at . as opposed to .1. For most installations it will be equivalent but apparently there are some objects defined under .0 and .2 so let's include them. > b) start at mib-2, but print a message to stderr (much like we do when we > default to stderr for logging) > pros: user advised that only a portion of mib is being used > cons: slight change in behavior (can be mitigated with config token to > disable message) This is just annoying - in this case I think the 'do nothing' option is better. > 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 I can support but users might be annoyed. (and my nit of . vs. .1 still apply) So, my preferred order would be c) a) <do nothing>) b) /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
