Robert,
in the last day or so, I've started getting warning
messages from snmpd (CVS MAIN):
"cache has existing timer id."
A bit of extra debugging code seems to indicate that this
relates to the ifTable cache, and it turns out that this
is being triggered by the initialisation of the ifXTable:
#0 netsnmp_cache_timer_start (cache=0x92a28c8)
at cache_handler.c:200
#1 netsnmp_cache_handler_get (cache=0x92a28c8)
at cache_handler.c:263
#2 _ifXTable_initialize_interface(
reg_ptr=0x92a74a0, flags=0)
at if-mib/ifXTable/ifXTable_interface.c:325
325 handler = netsnmp_cache_handler_get(
ifXTable_if_ctx.cache);
I'm presuming that both the ifTable and ifXTable share
the same cache structure (which seems sensible). But
what confuses me is that this has only just started
happening - it was fine a few days ago. And I can't
spot any changes to the "if-mib" code or cache handler
that look remotely relevant.
Any ideas?
Dave
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
