Re: cache problems with table data mib2c
Kathy McLeod <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <OF2C457748.9C4419F6-ON86257745.004E6C97-86257745.004E96A4@us.ibm.com> |
Hi -
I said that wrong. I meant should I add it to all the Reserve1 sections
for the other columns (vs. the the action section, for example). That
error code is what mib2c generated for the get section, so I went with
that.
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/17/2010 02:47 Subject
AM Re: cache problems with table data
mib2c
On 16 June 2010 20:14, Kathy McLeod <[email protected]> wrote:
> Problem 1: When I tried to do a set for a row that doesn't exist, I was
> getting a seg. fault (I was seeing set handler 4 debug msg but not the
next
> one). I added that check from the get section to the switch for the
> PortConfigStatus set section, and now it fails nicely (set handler 1b
debug
> msg). Is this the correct check?
Basically, yes - though the correct error code is actually
'SNMP_ERR_NOCREATION'
> Should I add it to all the column set sections
No - handling this in MODE_SET_RESERVE1 should be sufficient.
(The agent will then call 'MODE_SET_FREE', so that code would also
need to be ready to handle a missing row. But since that particular
block is empty here, there's no problem!)
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