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. Replaceexec ${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.
pgpGDDcidmqva.pgp
Description: PGP signature
------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
