First, let me say that things had been working fine. Lately we've been putting a greater load on authdaemond, and we've started experiencing sporadic auth failures that are logged like this:
SASL authentication failure: cannot connect to Courier authdaemond: Operation now in progress I've seen the excerpt from authdaemonrc: # PLEASE NOTE: Some platforms may experience a problem if there's more # than one daemon. Specifically, SystemV derived platforms that use # TLI with socket emulation. I'm suspicious of TLI's ability to handle # multiple processes accepting connections on the same filesystem domain # socket. # # You may need to increase daemons if as your system load increases. # Symptoms include sporadic authentication failures. If you start # getting authentication failures, increase daemons. However, the # default of 5 SHOULD be sufficient. Bumping up daemon count is # only a short-term solution. The permanent solution is to add more # resources: RAM, faster disks, faster CPUs... This is a Solaris 8 system so I'm already worried. Before, daemons=5 was sufficient; atm it is daemons=25 and I still get failures. I'm about to try cranking it again, but I get the feeling it isn't going to help... so I thought I'd ask here since Google didn't come back with anything. Should I continue to increase daemons until the problem goes away, or try to offload some of the authentication, or change OS's (heh)? Thanks in advance. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
