Wolfgang Fritz wrote: > Tommy Christensen wrote: >> Hi Wolfgang >> >> Yeah, memory leaks can be really nasty to track down. >> >> I am running with this patch on top of 5.0.8 - and I don't see >> any more leaks on SET requests! Perhaps it will work for you too, >> or at least provide some usefull hints. >> >> -Tommy >> > > Hi Tommy, > > the patch applied (with offset) to 5.0.9 and my first tests indicate > that it is working and removing the memory leaks. > Resurrecting an old thread here. Question: Do we have an idea of how many bytes are lost on a per-Set basis?
Perhaps a better question is: How do I check available memory in Linux? This way I can do a memory check before and after doing Sets. Then I can do an infinite loop of Sets and see how long it takes me to die. Would stopping and restarting the agent free up the leaked memory? Thanks, Carlos ------------------------------------------------------- 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
