wilfred I actually took a different approach but you pointed me in the right direction. Thanks!
What I ended up doing is setting the ownership and perms on Xvnc the same way SUN does for Xsun. Its more secure that way. Also, The reason your having to reset your directory perms is because /tmp is a virtual file system and gets cleared everytime the system reboots. If you reset the perms on Xvnc as I did you won't have to deal with that anymore, and you'll be able to run Xvnc as a non-root user. Thank again! --- [EMAIL PROTECTED] wrote: > On Wed, 17 Mar 2004, Hi Tech wrote: > hi, > > i guess that's the same old problem I have every > time my workstation > gets rebooted: the permissions of > /tmp/.X11-unix > are set to not allow arbitrary users to create a > socket (special file) in > there. > > Change permissions of above listed directory and try > again. > > HTH. > > Bye > Wilfried > > > Trying to run Tight VNC on Solaris 8 the following > > messages are displayed: > > > > _XSERVTransSocketCreateListener: failed to bind > > listener > > _XSERVTransSocketUNIXCreateListener: > > -- > # [EMAIL PROTECTED], no .sig today # > __________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
