Saslauthd memory leak ?

[Yann Rouillard]

> 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.

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