Re: non contiguous column index
"Dave Shield" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On 30/01/07, Renaud Barbier <[email protected]> wrote: > Here is the initialization code from one of the table in XXX_tables.c > as generated by mib2c. > /** Define the minimum and maximum accessible columns. This > optimizes retrival. */ > table_info->min_column = 1; > table_info->max_column = 13; OK - that's where you need to concentrate. This is saying that all columns from 1-13 are valid, which isn't true in your case. In order to handle non-contiguous columns sensibly, you should replace this with a suitably structured column specification. The field 'table_info->valid_columns' is a linked list of 'netsnmp_column_info' structures - use that to define which columns are valid or not. 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