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 simple way to mix having a virtual shared folder setup with a
separate PAM-based authentication procedure.
Replace “five” with “ten”, in the given example.
I'm not sure I understand the point you're making, possibly due to my
misunderstanding how authdaemond works.
It means that this approach will fail no matter how many authdaemond
processes you have configured. If you set the number of processes to X,
then if X connections arrive nearly simultaneously, then they will fail.
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 courier-authlib setup, if I configure X authdaemond processes to
start, and then if X+1 connections arrive simultaneously, what is
supposed to happen? If one of the connections will timeout and fail,
then is there another solution aside from increasing the number of
authdaemond processes started? I apologize in advance that I don't
understand enough to read the source code to find the answer.
Thanks,
-- Johnny Lam <[EMAIL PROTECTED]>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
