Saslauthd memory leak ?

[Igor Brezac]

On Tue, 18 Oct 2005, Yann Rouillard wrote:

>
>> This is a known issue with certain pam implementations.
>>
>>>
>>>> You can use saslauthd -n0, but this performs poorly
>>>> because saslauthd has to spawn a new process for each authentication.
>>>
>>> Thanks for the idea, I will try anyway if the performance impact is
>>> acceptable.
>>>
>>
>> You can probably use saslauthd -a getpwent or -a shadow instead.
>
> You were right, using shadow solved the problem.
>
> However I tried -n0 option but it didn't work, because saslauthd was
> compiled with ipc_doors which doesn't support the -n options.

Why do you need ipc_doors?

Make sure you built saslauthd with -D_REENTRANT, otherwise your current 
config will have problems.  For ipc_doors you need the mechanisms to be 
thread-safe and I do not think pam qualifies completely.

>
> I think it would be nice to mention in the man or somewhere in the doc.
>

What would you like mentioned?  You can always submit a patch.

-- 
Igor