On 21/02/07, Frank Fock <[EMAIL PROTECTED]> wrote: > I have placed this issue on the AgentX mailing list > and reached consensus regarding the "null object > identifier" usage.
Yes - I've been following the discussion. > Do you have an estimation in which NET-SNMP version > this fix will be available? We're currently in the (early) process of releasing 5.2.4, so it's an ideal time to fix that particular line. Fixes for the 5.3.x and 5.4.x lines will take a little longer, but I can get the patch applied so it's ready to roll out. > BTW, I have implemented a few workarounds into > SNMP4J-AgentX and AgentX++ to cope with some bugs > of the NET-SNMP subagent. Are interested in the > details? Most Definitely! I've been pulling together the outstanding bugs on our tracker system, so it would be good to get as much of this sorted as possible. A clear analysis of where things have gone wrong is invaluable. > There seem also to be 64bit OS related bugs > when encoding an IpAddress on AgentX. That wouldn't surprise me either. Let us have what you've got, and we'll see what we can do. Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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
