On Fri, 2005-02-04 at 17:37, Magnus Fromreide wrote: > On Fri, Feb 04, 2005 at 11:26:37AM -0500, Michael P. Soulier wrote: > > I see that the types that can be returned > > from a script called via pass or pass_persist are as follows: > > > > "The second line should be the TYPE of value returned, where TYPE is one of > > the text strings: string, integer, unsigned, objectid, timeticks, ipaddress, > > counter, or gauge." > > > > There are more types in snmp than this. > > Yes, you are right - they have missed counter64 and opaque in that collection.
It's arguable whether it's worth supporting OPAQUE, since this is almost never used in practise (our floating point type apart), and it would require a detailed knowledge of BER encoding within the pass-through script. But Counter64 would be a useful addition. This is actually a symptom of a deeper problem, in that the "pass" extension API only really supports SNMPv1 style behaviour. In particular, a GET request cannot distinguish between 'noSuchObject' and 'noSuchInstance' exceptions, and the SET handling can't report back most of the SNMPv2 errors - just 'notWritable' and 'wrongType' > I suppose the pass support could use some updating, or at least that > the man page could use it if it is fixed in the code. No - it's a problem in the code, rather than the documentation. If you do get around to updating this, please let me know so I can adjust the relevant section in the book. Dave ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
