On 18/09/06, Alon Marx <[EMAIL PROTECTED]> wrote: > In a table definition, what should the MAX-ACCESS values be for regular > columns (not indexes and not rowstatus)? Should it be read-write or > read-create?
Depends on the table. If you can create new rows in the table via SNMP SET requests, then you should use "read-create". If new rows are created "internally" (i.e. reporting what's happening elsewhere), then use "read-write". The most important thing is that you can't mix-n-match. All (writeable) column objects must have the same access value - either all read-write, or all read-create. You can't have both in the same table. > And does it make any difference when using mib2c? If the columns are defined as read-create, then the generated template will include code for handling row-creation. If they're defined as read-write, then it won't. Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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
