Sorry to pop in with silly questions... I had to do this same thing a few
weeks ago, and I wrote a perl script to completely walk the table, and keep
track of which rows were 'complete', since the walk is by columns, and this
table changes almost instantly (so I would end up with incomplete rows at
the end). Quite a script!

However, I didn't know there were scripts already for that? are we talking
of mib2rules package? which scripts are these?

Thanks,

Leo

On Tue, Jan 31, 2012 at 9:27 AM, Dave Shield <[email protected]>wrote:

> On 26 January 2012 17:30, Francois Bouchard <[email protected]>
> wrote:
> > In our SNMP agent, there is a table of data that we need to acquire from
> a
> > text file.  These data are read only, but can change within seconds in
> the
> > text file.
>
> How large is the table, and how quickly does the data change?
> How is this information likely to be used on the management side?
>
> The main problem with rapidly-changing data (particularly if rows are
> being created and destroyed), is that the management clients can
> easily find the table changing under its feet.
>   Plus if the table is large, then there can be a noticeable overhead
> in loading and parsing the table data for each individual incoming request.
>
> It's often useful to take a 'snapshot' of the current state of this table,
> and
> cache this within the agent for a little while.   Subsequent requests will
> then be processed from this cached version, rather than reloading the
> data afresh each time.
>
> The cache timeout can be set relatively low (e.g. one or two seconds),
> as long as this is sufficient to cover a full walk of the table.
>
>
>
> > I was wandering which script for table is the most recent one?
>
> I'm not entirely sure what you mean by the "most recent" table framework,
> or how useful this information would actually be to you.
>
> Most of the table frameworks would allow you to hold a local cache,
> and work in the way described above.
>
> Personally, my template of choice tends to be 'table_data'
> so I'd probably start by running
>
>    mib2c -S cache=1  -c mib2c.table_data.conf   myTable
>
> and work from that.
> Others (Robert in particular) prefer the MfD framework, which also
> supports the option of a local cache.   You've get that by running
>
>    mib2c   -c mib2c.mfd.conf   myTable
>
> and answering the questions it asks.
>
> You pays your money, and you takes your choice.
>
> Dave
>
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> 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
>
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
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

Reply via email to