On 19 October 2011 07:53, Ravi Kumar <[email protected]> wrote:
> I was going though netSnmpHostsTable table implementation based
> on mib2c.iterate_access.conf.
> I could no find a GETNEXT handling in netSnmpHostsTable_handler from the
> code looks like only get and set are handled.
That's correct.
Most of the table helpers have sufficient information within the
helper about which rows are valid, so they can determine the
appropriate "next row" within the helper code.
This means that a GETNEXT request can be converted
to the equivalent GET request, before being passed to the
MIB-specific handler.
So the MIB-specific code only needs to be concerned with GET/SET,
and doesn't need to worry about the (more complicated) GETNEXT processing.
Dave
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
