fully somebody will review, and commit.
Regards,
- Eivind
- Original Message
From: Robert Story
To: Eivind Naess
Cc: [email protected]; Dave Shield
; Wes
Sent: Wed, February 23, 2011 6:03:43 PM
Subject: Re: Constant polling of the interface stats in if-mib
On Wed, 1
On Wed, 16 Feb 2011 10:44:59 -0800 (PST) Eivind wrote:
EN> Sorry for sending this email again, but I cannot seem to be able to access
the
EN> sourceforge page to submit my patch. Does you or anyone else have problem
EN> accessing the patch tracker and click "Add New"? I get a HTTP 500 error
res
al Message
From: Eivind Naess
To: Dave Shield
Cc: [email protected]
Sent: Fri, February 11, 2011 8:20:26 PM
Subject: Re: Constant polling of the interface stats in if-mib
Good Morning Dave,
Thanks for your most excellent suggestion (and code review), the change becomes
ifTable_rowreq_ctx*) ITERATOR_NEXT(it);
return 1;
}
- Original Message
From: Dave Shield
To: Eivind Naess
Cc: [email protected]
Sent: Fri, February 11, 2011 9:59:09 AM
Subject: Re: Constant polling of the interface stats in if-mib
On 11 February 2011 17:37, Eiv
On 11 February 2011 17:37, Eivind Naess wrote:
> If you pay careful attention to the Interface_Scan_Init, it will dispose of
> the
> container for interface statistics and create a new container which in case
> triggers a full table re-load. Looking at the code for if-mib/ifTable, it uses
> the c
Guys,
I am setting up snmpd on a ARM device with network drivers that supports the
mii-ioctls, and I found that the host resources mib (hosts/hr_network.c)
invokes
the if-mib's interface for every table iteration of the host mib (via the
Interface_Scan_Init and Next functions).
The problem t
