-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo,
Thank you for updating the MainConfig web page.
This is what I decided to put in for that value. Currently dovecot runs
about 4 days before it starts to fail authenticating users. I did a
quick count on how many times auth-worker is called
On Mon, 2008-10-06 at 08:53 -0600, CJ Keist wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Timo,
>Thanks. Is there a good rule of thumb of what value I should put in
> for this?
The lower it is, the more CPU Dovecot uses by restarting the
dovecot-auth processes. But if it's t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo,
Thanks. Is there a good rule of thumb of what value I should put in
for this? The http://wiki.dovecot.org/MainConfig doesn't talk about
this config parameter.
Timo Sirainen wrote:
> On Oct 4, 2008, at 6:53 PM, CJ Keist wrote:
>
>> auth-wo
On Oct 4, 2008, at 6:53 PM, CJ Keist wrote:
auth-worker(default): pam(KVogel22,74.125.78.25): pam_authenticate()
failed: Dlopen failure
Set this to non-zero:
# Number of auth requests to handle before destroying the process.
This may
# be useful if PAM plugins leak memory.
#auth_worker_max
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Running Dovecot 1.1.3 and after dovecot has been running for awhile it
will just stop authenticating. Only fix is to stop and restart dovecot.
Here is the errors in the logs:
ct 4 09:34:32 goku dovecot: [ID 107833 mail.info] auth-worker(default):
p
