Re: cache problems with table data mib2c
Kathy McLeod <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <OF79BD9A7D.598D3D11-ON86257744.004EA287-86257744.004F0C1C@us.ibm.com> |
Hi -
In your previous note, you said to "Try tweaking the injection of the cache
handler to use 'TABLE_HANDLER_NAME'
rather than 'TABLE_TDATA_NAME'."
In this note, you say, "If you insert the cache helper using
'TABLE_HELPER_NAME', then you end up
with
cache -> table -> container -> tdata..."
so is it Handler or Helper?
The code I sent you is the one I tested with yesterday, and it is NOT
working fine. (I am generating the data and not calling the backend). I
will try "HELPER" later today and see if that changes anything. But
otherwise, are you saying the code I sent you always worked with no seg.
faults? (the unload/load works, but did the commands after all work?)
Thanks.
Kathy McLeod
Dept S82 CCB - SNMP
IBM Rochester, MN
(507) 253-4803
Dave Shield
<D.T.Shield@liver
pool.ac.uk> To
Sent by: Kathy McLeod/Rochester/IBM@IBMUS
dave.shield@googl cc
email.com net-snmp users
<[email protected]
et>
06/16/2010 02:55 Subject
AM Re: cache problems with table data
mib2c
On 15 June 2010 21:46, Kathy McLeod <[email protected]> wrote:
> I think your diagnosis is correct. It is setting up for the row and
column
> in the old table and then when those rows are not in the new table, I get
> errors. This does not seem correct to me - isn't the point of reloading
to
> have the latest and greatest before the handler is called?
Yes.
Or more accurately, to have the latest-and-greatest reloaded
before the handler which decides which row of the table is required.
There are four helper handlers that are relevant here:
table: which handles table indexing
table_container: which handles table rows
table_tdata: which hides some of the inner working of
table_container
cache: which handles the cache
The vital one is 'table_container', which looks at the content of the
container, and decides whether the request is valid, and which row
of the table to work with.
If you insert the cache helper using 'TABLE_TDATA_NAME', then you end up
with
table -> container -> cache -> tdata
So the container helper gets invoked before the cache helper, and hence
is working with an old or empty container.
If you insert the cache helper using 'TABLE_HELPER_NAME', then you end up
with
cache -> table -> container -> tdata
So the cache helper gets invoked (to populate the container) before the
container helper, and the container helper can work with up-to-date info.
> Here are my results:
I suspect that the problems you are seeing now must relate to the
interface between your MIB module and the underlying subsystem.
The version you posted (with dummy data) seems to be working fine.
Dave
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
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