On 12 April 2010 02:36, Robert Story <[email protected]> wrote: > On Sun, 11 Apr 2010 19:53:23 +0000 Scott wrote: > GS> When I set the MAX-ACCESS for a RowStatus to read-only in the MIB then > smilint reports: > GS> "[4] {rowstatus-access} warning: illegal `RowStatus' access value" > GS> > GS> So I'm trying to figure out if the table is always going to be read only > GS> if I should include RowStatus or not and what to use for the MAX-ACCESS > GS> value. > > Interesting. It seems that smilint is being overly strict in interpreting > section 7.1.12.1 of RFC 2578, which says that RowStatus MAX-ACCESS for tables > that allow row creation is read-create. It doesn't say anything about using > RowStatus in tables which don't allow row creation.
Given that the whole purpose of the RowStatus convention is to control the creation and deletion of rows from a table - then it seems reasonable to assume that if a table contains such a column, it will be used for that. And if the table is read-only, then this cannot work as expected. So I would suggest that smilint is behaving correctly in flagging up this situation. Particularly since it's issuing a warning, rather than an error. My take on this would be that if the table doesn't allow rows to be created or deleted dynamically via SNMP SET requests, then it should not contain a RowStatus column in the first place. Dave ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
