On Thu, 7 Jun 2007 11:01:47 -0700 (PDT) Need wrote: NH> A) You stated there are other methods (instead of using "se_add_pair_to_slist" and "se_find_value_in_slist" routines) which can be used to remember index values. I assume "other methods" mean that I am free to implement any other way to remember index values if I want :>) ... or perhaps other methods already exist within NetSNMP? I asked this question, since it does seem silly to assign a "text string" to each index value like the "se_xxxx" routines mentioned above require in order to remember the index mappings. I might see if I can find another way without using text strings. Any advice?
The slist stuff is just the easiest out of the box. If the devices have any sort of unique identifier, you could simply maintain a table of thosse identifiers and an unique id. NH> C) Just wanted to confirm with you the following is true .... please confirm: NH> NH> The "_mfd_ocStbHostAnalogVideoTable_object_lookup()" routine calls the "ocStbHostAnalogVideoTable_row_prep()" routine and now it is possible for the "ocStbHostAnalogVideoTable_row_prep()" routine to return a MFD_SKIP value. This means the "_mfd_ocStbHostAnalogVideoTable_object_lookup()" routine can now return a MFD_SKIP value. NH> NH> I just wanted to confirm that this is ok and no additional code is required (somewhere else) to handle a MFD_SKIP value from being returned by the "_mfd_ocStbHostAnalogVideoTable_object_lookup()" routine. The interface.c code for each table will have to be updated to handle the new return code. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
