On 23/08/06, Robert Story <[EMAIL PROTECTED]> wrote: > DS> Ideally (IMO), this module should be written to use the cache_handler, > DS> rather than manipulating the cache itself. That would allow the > DS> cache timeout, etc, to be controlled dynamically via the > DS> NET-SNMP-AGENT-MIB::nsCacheTable > > It does use the cache_handler. Does it need to do something special to work > with nsCacheTable?
My apologies. The ifTable OID does appear in the nsCacheTable, so it should be possible to manipulate this caching behaviour dynamically. Good - that's worth knowing for the future. (This question has come up two or three times very recently - an FAQ candidate, methinks!) > The ifTable is a special case, as I mentioned in my previous message. We need > to update the cache every 30 seconds to ensure 32bit counters don't wrap > before we poll again. This is documented in the comments where the cache > timeout value is set. Errr... I'm probably being dense, but I can't immediately see where. There's a comment about 32-bit wrapping next to the definition of IFTABLE_CACHE_TIMEOUT in ifTable_data_access.h. But there's nothing by the call to 'netsnmp_cache_create' in ifTable_interface.c And there's certainly no indication of what the difference between these two timeouts are, and why they are different. As far as I can tell, the 'netsnmp_cache_create' value doesn't seem to have any effect, but I've probably missed something vital. Dave ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
