We're seeing clients of saslauthd failing with "connection refused" with a load of around 10 queries per second under Solaris. Our saslauthd is using a PAM radius module. Some experimentation shows this error occurs on unix domain sockets when the server doesn't respond fast enough.
The radius backend consists of multiple backends behind a load balancing device, so it's reasonable to assume that increasing the saslauthd concurrency (fork more children) would resolve "connection refused" problem. I notice that saslauthd is hard coded to start exactly 5 children - I intend to make this a command line option, although I wondered if I'd missed something obvious since it seems an obvious enhancement? -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/
