Cyrus Data Loss / Cache corruption after

Andrew Morgan morgan at
Thu Mar 17 12:33:04 EST 2005

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 

Cyrus Home Page:
Cyrus Wiki/FAQ:
List Archives/Info:

More information about the Info-cyrus mailing list