> On Tue, 16 Jun 2009 08:37:13 +0100, Dave Shield
> said:
[FYI, I agree you've agreed on your agreements and I too agree]
DS> Of course, if you don't load the MIBs, then you need to specify numeric
DS> OIDs in the config file - and that would apply to the new cache timeout
DS> directive
2009/6/16 Robert Story :
> DS> No - it means that MIB object names in the config file would be converted
> DS> to numeric OIDs, presumably by the config parsing routine.
> DS>
> DS> Internally the comparisons would be of numeric OIDs, yes.
> DS> But the user visible config could use names or number
On Mon, 15 Jun 2009 22:21:27 +0100 Dave wrote:
DS> 2009/6/15 Robert Story :
DS> > if internal to the cache helper, that would mean OIDs in the conf file,
since
DS> > that's all the cache helper is passed..
DS>
DS> No - it means that MIB object names in the config file would be converted
DS> to n
2009/6/15 Robert Story :
> if internal to the cache helper, that would mean OIDs in the conf file, since
> that's all the cache helper is passed..
No - it means that MIB object names in the config file would be converted
to numeric OIDs, presumably by the config parsing routine.
Internally the c
On Mon, 15 Jun 2009 21:14:06 +0100 Dave wrote:
DS> > "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
> "cacheTime ifTable 30"... stuff the key/value pairs
> into one of dave's slists, and add lookup in the table init call..
I was actually thinking more along the lines of the table
initialisation code being left as it stands, and dealing with
the timeout configuration/lookup within the c
