On Thu, 17 Mar 2005, Gregory Harris wrote:
Last Friday, my saslauthd process (the default version on RHEL3) consumed up all of the memory on my mail server, making it very slow and some processes were force exited because of insufficient memory.
Regarding saslauthd, here's how I run it to prevent memory leaks from building up:
/usr/local/sbin/saslauthd -n0 -a pam
The -n0 means spawn a child process to handle every request (don't run with threads).
FYI, the memory leak is in the pam libraries apparently, not saslauthd itself.
Andy --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
