Subject: Re: saslauthd instability with sockets
From: Steve Barber (steveb at cme dot nist dot gov)
Date: Tue May 20 2003 - 13:26:10 EDT
On Tue, May 20, 2003 at 06:01:46PM +0300, Leena Heino wrote:
> Has anyone else noticed any instability with the saslauthd 2.1.13 and
> unix sockets.
On our Solaris 8 server with several thousand users, we've been using
UNIX sockets for the last year with no specific problems we can attribute
> It seems that in Solaris 8 and 9 saslauthd loses its ablity to communicate
> through socket. The socket is there, saslauthd processes are there, but
> for example imapd cannot connect to that socket.
We've not seen that here. Under what circumstances does this happen?
> Is ipc with doors more stable than ipc with unix sockets?
> Are there any other advatages with Solaris and ipc with doors?
We attempted to use doors with our last SASL build but it flopped.
Users were randomly getting authentication refused, and the
frequency seemed to correspond with the overall load of the machine,
although it did not have to be heavily loaded to observe the effect.
We tried this as part of our upgrade to 2.1.13. When it didn't work,
we fell back to our previous 2.1.10 build (using UNIX sockets) and
have not yet done anything more with it. It's not clear whether
the problems were due to the new caching code, other changes, or
the doors themselves. We'll probably try 2.1.13 with UNIX sockets
next to see if that works, hopefully in a test environment first.