> Well, no. I really appreciate your quick feedback and explanation but > now I'm worse off than I was. Before, my set routine got called n times > for port 1, now it doesn't get called at all!
Arggghhh - I'm a pillock! I've just spotted that you're talking about "snmp_add_var", which is one of the very few API calls that *does* take a printable representation of the value. Internally it then turns this back into a binary value, so it's a rather inefficient call to use in this case, but the original code was probably more-or-less correct. <Sigh> Maybe I better leave this to someone else..... Dave [Though I still don't understand how changing the internals of this routine would affect when it's called.....] ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ 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
