For a separate reason I was testing, too, and found the above
statement about Solaris to be true in 2.5 and 2.6, but not in 2.5.1.
(It's probably true in Solaris < 2.5, but I didn't test that.)
On my 2.5.1 test system a bind() to a UNIX domain named socket
creates the file system object mode 0, and a connect() to a UNIX
domain file system object with mode 0 is ECONNREFUSED. It appears
the listener process must do a non-zero chmod() of the file system
object after the bind has created it to allow another process to
connect to it.
Solaris 2.5 and 2.6 seem to create the UNIX file system object for
a UNIX domain socket with non-zero mode bits.
>Casper
Vic