Dave, turn-about is fair play, right? :-)
I was moving the notification_log mib stuff into the agent library today, and the cvs main version is based on table_dataset2. I've got 2 questions. The data2 structure has the table container netsnmp_index and it's own index_oid/index_oid_len (which is labeled 'backwards compatability'). Since this is a new helper, I would think that there would be no need for backwards compatability, and having 3 places to keep the indexes in sync would cause to much confusion (and indeed, the cvs main notification log mib leaked like a sieve because of a search on the wrong index). I've removed them in my local cvs, and things seem to work find w/out it. Next, the netsnmp_table_data2_build_result() function is marked obsolete, is empty and returns GENERR. However, it is still used by table_dataset2 for get processing. In this state, the notification log mib doesn't work. Restoring the code (based on the table_data verstion) fixes things. A quick search didn't turn up a suitable replacement. What am I missing? -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
