>>>>> On Mon, 25 Apr 2005 17:08:20 +0100, "Andy Ford" <[EMAIL PROTECTED]> said:
Andy> Wes - thanks for responding with a patch. Unfortunately, it Andy> didn't work. I limited my perl script to the following but the Andy> memory issue still persists... Andy, I've spent *waaaayyy* to much time tracking this down. I now know quite a bit more about perl internal programming, which I always meant beef up my knowledge on. I doubt I'll remember it tomorrow though (sigh). Anyway, the main-line CVS TrapReceiver.xs file is now completely memory leak free. Note that there are a number of things you should consider when debugging memory with snmptrapd: 1) get the latest TrapReceiver.xs from cvs as mentioned above (I can mail it to you if you really can't get to the cvs tree; see http://www.net-snmp.org/cvs/ for details). 2) note that snmptrapd keeps logs around of the last few traps sent to it. This will make it appear that memory is growing, though it should eventually top out. To turn this off so it never saves anything, put this following line in your snmptrapd.conf file: dontRetainLogs true With those two in place my process never grows and vagrind shows no leaks. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ 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
