Re: cache problems with table data mib2c
Dave Shield <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On 17 June 2010 15:18, Kathy McLeod <[email protected]> wrote: > 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). This error (noCreation) needs to be returned for all MIB column objects in that table, so needs to be present in each of the cases in the 'switch(colnum)' block. (Apart from default, which should return 'notWriteable') It doesn't really matter which pass this is handled in - Reserve1, Reserve2 or Action. But since you know the request is going to fail, it makes sense to report this as soon as possible. Otherwise, you might find assignments to other MIB objects in the same SET request being processed in the Action pass, before this table rejected the request. Those assignments would then have to be reversed. Rejecting the request during Reserve1 will avoid applying these updates in the first place. 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