On Friday, June 25, 2010 04:30:45 pm Wes Hardaker wrote:
> > Hi i'm looking at net-snmp code to understand the main flow of the
> > requests that come/go. I'm looking at netsnmp_register_handler
> > (agent_handler.c:207) As far as i understand it makes some checks and
> > passes the
> > netsnmp_han
> Hi i'm looking at net-snmp code to understand the main flow of the requests
> that come/go. I'm looking at netsnmp_register_handler (agent_handler.c:207)
> As far as i understand it makes some checks and passes the
> netsnmp_handler_registration *reginfo to netsnmp_register_mib function to
>
> but as far as i understand the netsnmp_call_handler (agent_handler.c) already
> traverses all of the handlers in the list (handler->next) and calls each of
> them's access_methods is it necessary to call netsnmp_call_next_handler in my
> hanldlers ?
You only need to call it if you have handl
Hi in iftable (/net-snmp-5.5/agent/mibgroup/if-mib/ifTable/ifTable.c) code i
see that a handler that handles a scalar calls netsnmp_call_next_handler ,
static int
_if_number_handler(netsnmp_mib_handler *handler,
netsnmp_handler_registration *reginfo,
n
On 06/24/2010 06:01 PM, Dave Shield wrote:
> On 24 June 2010 15:19, Magnus Fromreide wrote:
>>> I suspect that what is probably needed is some form of flag within the
>>> range_list structure, to indicate whether the values should be treated as
>>> signed or unsigned (with appropriate casts if nec
Hi i'm looking at net-snmp code to understand the main flow of the requests
that come/go. I'm looking at netsnmp_register_handler (agent_handler.c:207)
As far as i understand it makes some checks and passes the
netsnmp_handler_registration *reginfo to netsnmp_register_mib function to
register it
