Virtual Memory Consumption of Cyrus IMAPd

Wil Cooley wcooley at
Tue Jul 20 14:18:10 EDT 2004

On Tue, 2004-07-20 at 10:58, Mohamed Magdi Abbas wrote:
> Rob Siemborski wrote:
> > On Mon, 19 Jul 2004, Andrew Brink wrote:
> > 
> >> I have also seen this sasauthd memory leak on a Debian box.  A simple 
> >> restart always fixes the problem for me too.
> > 
> > 
> > When we get reports like this it inevitably turns out to be the PAM 
> > module leaking memory, not saslauthd itself.
> But then why would a restart of saslauthd itself fix things, i.e. 
> release the swap space (it or someother piece down the line) used up?

Because the PAM modules are dynamically loaded, like libraries, which
saslauthd calls into.  These modules are part of the saslauthd process,
so when they leak memory, the whole process space grows.

Wil Cooley                                 wcooley at
Naked Ape Consulting              

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :

More information about the Info-cyrus mailing list