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
>
> 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)
>
> 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
>
>
> Thoughts?
I'll vote for b):
- It doesn't break any tools which rely on mib-2 being the one shown if
no starting point is given,
- the warning is given on stderr which is usually redirected to another
destination.
Josef
--
These are my personal views and not those of Fujitsu Technology Solutions!
Josef Möllers (Pinguinpfleger bei FTS)
If failure had no penalty success would not be a prize (T. Pratchett)
Company Details: http://de.ts.fujitsu.com/imprint.html
------------------------------------------------------------------------------
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
