On Mon, 15 Jun 2009 21:14:06 +0100 Dave wrote: DS> > <rstory> "cacheTime ifTable 30"... stuff the key/value pairs DS> > into one of dave's slists, and add lookup in the table init call.. DS> DS> DS> I was actually thinking more along the lines of the table DS> initialisation code being left as it stands, and dealing with DS> the timeout configuration/lookup within the cache helper.
hmm... ok.. but the basic idea is the same as mine. read the config, save the values somewhere, right? doesn't seem all that complicated... if internal to the cache helper, that would mean OIDs in the conf file, since that's all the cache helper is passed.. DS> DS> That way *all* cached tables would pick up run-time configuration DS> automatically, without needing to update per-module code. I don't know if that's possible. Some modification will be needed... For example, the ifTable creates the cache in once place with a generic default time, but then sets the final value in another place. An idiosyncrasy of it being MfD code.. DS> Of course, this should also handle the persistency of SETing DS> these cache timeouts. persistence is a whole other wrinkle. If the default is 30, the conf file sets it to 15, but at runtime it is set to 45, and the agent shuts down. When the agent starts again, what value should it use? I guess rows with values from the conf file could be make read-only... But persistence could be done later, don't you think? ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
