> Ok, then since there is now a new table to fulfil your craving for a > 'correct' module ;-), what about reverting the old extTable to it's > original implementation?
As I recall (and this is going back a fair while now!), the thing that broke wasn't actually the MIB implementation code - it was the utility function for running a subcommand. The original version was very tightly tied in to the expectations of the extensible table, and that's where the caching was done. Not in the extensible module itself. I seem to remember that I was trying to make the subcommand handling more flexible (so I could use it somewhere else - probably the trap handler), so stripped out the caching element. In order to revert to the previous behaviour, it would be necessary to insert equivalent (new) code into the extensible module var_ routine to handle the caching. That's certainly possible, but I'm afraid I don't have the time to address it. Or the inclination, to be honest - I felt it was a better use of my time to tackle doing this "right", rather than patching up a creaking (and IMO fundamentally broken) MIB. Dave ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Net-snmp-users mailing list [EMAIL PROTECTED] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
