>I'm getting the following error running vncserver under Solaris 7
>as a non-root user:
>_XSERVTransSocketCreateListener: failed to bind listener
>_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
>_XSERVTransMakeAllCOTSServerListeners: failed to create listener for local
>Fatal server error:
>Failed to establish all listening sockets
>xrdb: Interrupted system call
>xrdb: Can't open display 'sparc2:1'
>xsetroot: unable to open display 'sparc2:1'
>xterm Xt error: Can't open display: sparc2:1
>It works when I run su to root before starting vncserver.
>Under Slackware Linux I get no errors starting as root or non-root user.
>Any suggestions?
Sorry, forgot to RTFM - from the VNC FAQ:
Q11: I get errors like "failed to bind listener" and "Failed to establish
all listening sockets" in the log file.
This is probably due to the permissions on /tmp/.X11-unix. You may
well see this if you update to Solaris 2.7 or Redhat 6.0, for example.
See the section below entitled "Why can I only run vncserver/Xvnc as root?".
Q20: Why can I only run vncserver/Xvnc as root?
The most likely reason for this is that Xvnc can't create the unix domain
socket
(the path for this unix domain socket is usually /tmp/.X11-unix/Xn). Try
making
sure that users can write to this directory by making it world-writable,
i.e.
"chmod a+w /tmp/.X11-unix". Note that to avoid a security loophole the
"sticky bit"
should also be set on the directory by doing "chmod o+t /tmp/.X11-unix".
If you don't do this then someone else logged in to the same machine may be
able to intercept the X protocol and thereby access your desktop and snoop
on
it, etc. An alternative is to set the Xvnc binary to have the same
permissions as
your normal X server, but this may be more of a security risk.
by