>>>>> On Sun, 21 Nov 2010 17:17:45 -0500, Doug Manley <doug.man...@gmail.com> >>>>> said:
DM> This made absolutely no sense to me and I almost never caught it Unfortunately there is pretty much no way to determine what the cause might be without you running your daemon in a debugger. The only possibility I can think of is if you're actually succeeding in wrapping a 16bit int (IE, you have a request outstanding that is older than 2^16 later requests) and thus duplicating a session with two identical requestIDs. Your daemon would need to be sending a huge number of requests to see this (and they'd likely be odd as well). Or starting up a huge number of sessions. You could play with the code in snmp_api.c and only turn on the 16bit IDs for certain things (like the reqid but not the msgid and sessid) and see if that helps. DM> Is there a known problem with "netsnmp_ds_get_boolean" when the DM> boolean is actually set? The problem is certainly not with netsnmp_ds_get_boolean. -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
