Re: mib2c.table_data.conf, cache timeout period does'nt seems to change.

oups wrong button let me finish my post,

Is there defference in the code using mib2c* -S cache=1* -c
mib2c.table_data.conf myTable  * instead of*  mib2c -c
mib2c.table_data.conf my myTable, *option 1)* ?



Thanks
Francois

2012/2/10 Francois Bouchard <[email protected]>

> Hi,
>
>
> For tables implemented with the mib2c.table_data.conf script (option 1,
> for cache enabled) the default timeout period of 60 seconds is working well
> but when I lower that value with the
> #define statement (5, then 30) the timeout period stays steady at 60
> seconds)
>
>
> The code for the table is generated with the script
>
>    mib2c -c mib2c.table_data.conf my myTable, option 1)  Hold a local
> cached copy of some external data which is then used to service incoming
> requests.
>
>
>
>
>
>
>   mib2c -Scache=1  -c mib2c.table_data.conf  myTable
>
>
>
>
> I'll try some other stuff today.
>
> Francois
>

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/

_______________________________________________
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