Hi, And my mail refused due to attachment, so I posted it here: http://www.kovoks.nl/authdaemond.log.gz
Tom Albers KovoKs B.V. KvK: 11033334 Citeren Tom Albers <[email protected]>: > Forward to mailing list since I received no reaction yet.... > > Best, > > Tom Albers > KovoKs B.V. > KvK: 11033334 > > > > ----- Doorgestuurd bericht van [email protected] ----- > Datum: Sat, 14 Aug 2010 23:34:33 +0200 > Van: Tom Albers <[email protected]> > Antwoorden aan:Tom Albers <[email protected]> > Onderwerp: Re: [courier-users] Auth daemon memory leak. > Aan: Sam Varshavchik <[email protected]> > > Quoting Sam Varshavchik <[email protected]>: > >> Tom Albers writes: >> >>> Sam, >>> >>> Attached is the logfile. I hope it is useful. >> >> Sorry, I made a small mistake. I forgot that $sbindir/authdaemond is a >> shell wrapper script, not the real binary that ends up running in the >> background. >> >> Please rollback the change, and edit the authdaemond script itself. >> >> Replace >> >> exec ${sbindir}/courierlogger -pid=/var/spool/authdaemon/pid >> $LOGGEROPTS -$1 /usr/libexec/courier-authlib/authdaemond >> >> with >> >> ${sbindir}/courierlogger -pid=/var/spool/authdaemon/pid $LOGGEROPTS -$1 >> valgrind --tool=memcheck --leak-check=yes --log-file=/tmp/authdaemond.log.$$ >> /usr/libexec/courier-authlib/authdaemond & >> >> This is one line. Hopefully this'll do the trick. After starting >> authdaemond and replicating the problem, make a copy of the log file >> before stopping authdaemond. You'll need to stop it by killing the >> process, rather then executing the stop command -- because of the way >> valgrind gets shoved into the pipeline, the regular stop command won't >> work. >> >> By having the pid appended to the generated log filename >> /tmp/authdaemond.log.$$ this will prevent anything useful from being >> overwritten if the wrapper script gets executed again, by mistake. >> >> You can either mail the logs to me, or post it somewhere I can grab if >> my spam filters bounce it, rather than posting the whole thing to the >> list. > > > > Hi, > > Thanks for the help. I had to improvise a bit to get the log, i've > seen that multiple processes has logged in the log unfortunately, but > I hope that's not that crucial for the analysis. > > See attachment. > > Met vriendelijke groet, > > Tom Albers > KovoKs B.V. > KvK: 11033334 > > > ------------------------------------------------- > Dit mailtje is verstuurd vanaf de server van KovoKs. > http://www.kovoks.nl > > > > ----- Einde doorgestuurd bericht ----- > > > ------------------------------------------------- > Dit mailtje is verstuurd vanaf de server van KovoKs. > http://www.kovoks.nl ------------------------------------------------- Dit mailtje is verstuurd vanaf de server van KovoKs. http://www.kovoks.nl ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
