Sam Varshavchik wrote:
Johnny Lam writes:
The script takes an "AUTH" request, checks the username/password using
the "chkpw_pam" program, then makes a separate connection to
authdaemond to make a "PRE" request to return the account data. Since
authProg simply sends "FAIL" for a "PRE" request
Johnny Lam writes:
Sam Varshavchik wrote:
Johnny Lam writes:
The script takes an "AUTH" request, checks the username/password using
the "chkpw_pam" program, then makes a separate connection to
authdaemond to make a "PRE" request to return the account data. Since
authProg simply sends "FAIL
Sam Varshavchik wrote:
Johnny Lam writes:
Sam Varshavchik wrote:
There's one potential problem with this.
The default configuration setting runs 5 authdaemond processes.
You get five logins come in at the same time. You turn around and
reconnect to authdaemond, five times. Your connectio
Johnny Lam writes:
Sam Varshavchik wrote:
Johnny Lam writes:
Sam Varshavchik wrote:
There's one potential problem with this.
The default configuration setting runs 5 authdaemond processes.
You get five logins come in at the same time. You turn around and
reconnect to authdaemond, five t
Sam Varshavchik wrote:
Johnny Lam writes:
Sam Varshavchik wrote:
Johnny Lam writes:
Yes, that is true. I forgot to mention that I had doubled the
default number of authdaemond processes that are started from 5 to
10. Despite the increased resource usage, I'm pleased that there
was a sim
Johnny Lam writes:
Increasing the number of daemon processes does not totally eliminate the
problem, it only makes it less likely to occur.
You trimmed the question in my last post that essentially asked if this
same problem can occur with a default courier-authlib setup. In a
default cour
