Virtual Memory Consumption of Cyrus IMAPd
Mohamed Magdi Abbas
abbasmm at longwood.edu
Tue Jul 20 14:59:03 EDT 2004
Rob Siemborski wrote:
> On Tue, 20 Jul 2004, 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?
>
>
> PAM modules are used as libraries by the running process. If they leak
> memory as part of the saslauthd process, then killing saslauthd will
> release the leaked memory.
Ah, that's right... thanks for the reminder...
>
> -Rob
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
> Research Systems Programmer * /usr/contributed Gatekeeper
>
> ---
> 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
---
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
More information about the Info-cyrus
mailing list