On 08/20/14 21:58 +0200, Martin Sebald wrote:
So does the work around work anyway? It seems that I not fully understand what is going on. Anyway, if I restart saslauthd after the problem is there everything works right away like there was never a problem.
Yes, it should, since saslauthd spawns a new process (-n 0) with each authentication attempt. The memory gets freed when the process ends even though there's a memory leak. You'll hide the problem at the expense of process setup/tear down overhead. -- Dan White -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
