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

2012-02-15 Thread Francois Bouchard
Many Thanks, Francois 2012/2/15 Dave Shield d.t.shi...@liverpool.ac.uk On 14 February 2012 15:35, Francois Bouchard francois.bouch...@mpbc.ca wrote: Here is the code for a cached snmp table module. OK - I've tried compiling and running that module. The timeout specified in the header

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

2012-02-14 Thread Francois Bouchard
I'm sorry - I don't have the time to try and re-create the rest of the code that's missing here. If you want assistance with tracking down the problem, can you please post the *complete* code files, so that we can try compiling them into a working module. Here is the code for a cached snmp

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

2012-02-14 Thread Francois Bouchard
According to the documentation ( http://www.net-snmp.org/dev/agent/group__cache__handler.html), a changing the flags will change the behavior of the cache system. After some testing of my module, it is possible to state that the agent's data change almost instantly (when the external data

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

2012-02-13 Thread Francois Bouchard
Dave, you should be able to modify this timeout by editing the header file and recompiling the module. Yes this is what's been done, thexxxTable_free(...) isn't called in less than 60 seconds, even when lowering XXX_TIMEOUT in the header file. Perhaps you could post the code that you're

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

2012-02-13 Thread Dave Shield
On 13 February 2012 15:46, Francois Bouchard francois.bouch...@mpbc.ca wrote: Perhaps you could post the code that you're working with so that we can test this Yes, here is the code for the initialize function (generated using mib2c -c mib2c.table_data.conf mpbcRMHAlarmTable  (when asked :

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

2012-02-11 Thread Suresh kumar
is 60 seconds are minimum time for cache cleanup. ~Suresh Date: Fri, 10 Feb 2012 20:51:45 + Subject: Re: mib2c.table_data.conf, cache timeout period does'nt seems to change. From: d.t.shi...@liverpool.ac.uk To: francois.bouch...@mpbc.ca CC: net-snmp-users@lists.sourceforge.net On 10

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

2012-02-10 Thread Francois Bouchard
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 francois.bouch...@mpbc.ca Hi, For tables

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

2012-02-10 Thread Dave Shield
On 10 February 2012 15:02, Francois Bouchard francois.bouch...@mpbc.ca wrote: 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) ? Errr... that second form looks invalid. mib2c only takes a

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

2012-02-10 Thread Francois Bouchard
Hi, Sorry about the mistake, I was asking for hints about the cache timeout values. It can't be modify when changing the xxx_TIMEOUT define statement ( ie.e stays at 60 seconds ) Any hints? Francois But to answer your question - yes, I believe -S cache=1 *is* different to local cached

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

2012-02-10 Thread Dave Shield
On 10 February 2012 20:06, Francois Bouchard francois.bouch...@mpbc.ca wrote: I was asking for hints about the cache timeout values.  It can't be modify when changing the xxx_TIMEOUT define statement ( ie.e stays at 60 seconds ) H you should be able to modify this timeout by editing