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 -- Wil Cooley [EMAIL PROTECTED] Naked Ape Consulting http://nakedape.cc
signature.asc
Description: This is a digitally signed message part
