Zitat von Robert Krig <robert.k...@render-wahnsinn.de>:
On 01/13/2012 09:52 AM, lst_ho...@kwsoft.de wrote:Zitat von Robert Krig <robert.k...@render-wahnsinn.de>:On 01/11/2012 08:38 PM, Gary Smith wrote:Restarting postfix, saslauthd and authdaemon seems to get it working again, at least for a while.Are you using pam_mysql by chance?Yes, I am.Too bad, pam_mysql is known to leak memory. We have used it some time ago and the only option to get it "stable" was with "saslauthd -n 0". Regards AndreasSo far it's been running stable, memorywise by using the "-c" flag for cacheing. Is there any downside to the "-n 0" flag? I had read about before, but I wanted to see if cacheing alone made a difference.
The downside of "-n 0" is that for every authentication request a new process is spawned and ended afterwards so the memory leak will not sum up. This will hit performance limits because of init costs (process startup, db-connection etc.) if your authentication rate is very high. For small/mid-size systems it should not matter that much.
Regards Andreas
smime.p7s
Description: S/MIME Cryptographic Signature
