DS> No - that's not what I said. I suggested tweaking the 'name' parameter if there were no *rows* in the table - if it was completely empty. The idea was to skip calling the same handler 50 times, each of which returned an empty column.
DS> Note that the agent can't assume that a failure in one column will automatically mean a failure in the other columns - it's quite possible to have a "sparse" table, where individual values are missing. Or even for a particular column object not to be implemented at all. DS> he agent can't know whether to skip to the end of the table - only your code knows that. DS> Now I'm not too surprised if this doesn't actually work - as Robert says, such behaviour was regarded as "evil". But it was worth a try. I suspect that you may need to switch to using the v5 handler-based API if you want to be able to do this. Can v5 handler-based API do that? Could you tell me where to start? Thanks, FT ------------------------------------------------------- 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_idt77&alloc_id492&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
