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 connection requests will
timeout because no more authdaemond processes are available.
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. I thought that the number of
child authdaemond processes that were started determined the number of
simultaneous login attempts that could be handled, e.g., if daemons=5,
then one could handle only 5 simultaneous login attempts and no more --
additional login attempts would time out and fail. Is this correct? If
this is not right, could you explain the relationship between the
"daemons" setting and the simultaneous login attempts?
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
