On Wed, 2 Jun 2004 17:30:38 -0600 Carlos wrote: CC> Wolfgang Fritz wrote: CC> > Tommy Christensen wrote: CC> >> I am running with this patch on top of 5.0.8 - and I don't see CC> >> any more leaks on SET requests! Perhaps it will work for you too, CC> >> or at least provide some usefull hints. CC> > CC> > the patch applied (with offset) to 5.0.9 and my first tests indicate CC> > that it is working and removing the memory leaks. CC> > CC> Resurrecting an old thread here. Question: Do we have an idea of CC> how many bytes are lost on a per-Set basis?
I don't think specific numbers were ever posted. CC> Perhaps a better question is: How do I check available memory in CC> Linux? This way I can do a memory check before and after doing Sets. CC> Then I can do an infinite loop of Sets and see how long it takes me CC> to die. Hmmm.. well, there are various memory debuggers that will report lost memory, but I'm not familiar with the run-time APIs. I generally run 'top', and press 'M' to sort by memory, and watch the process climb to the top. It's not precise (eg reports in KB or MB), but it gives you a general idea. CC> Would stopping and restarting the agent free up the leaked memory? Yes. -- Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ 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
