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 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.
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.
pgpB4D3k8mrVg.pgp
Description: PGP signature
