[tbox-l] Yet another change request for /opt/freeware/bin/vncserver

[Markus A. <al...@de...>]

Folks,

there's been some discussion about changes to the 
/opt/freeware/bin/vncserver shell script and as we're on the topic, 
here's another thing that I'd like to bring forward.

This appears to be a fairly old problem (at least searching the web 
gives some hits pointing into the same direction). Here goes:

When starting vncserver without the "-nolisten local" option, it fails 
to execute the commands that I specify in ~/.vnc/xstartup and I get 
errors like these in ~/.vnc/<host>:<displaynum>.log:

AUDIT: Fri Jul  7 15:14:17 2006: 585912 Xvnc: client 1 rejected from 
local host
Xlib: connection to ":1.0" refused by server
Xlib: Client is not authorized to connect to Server
mwm: 2053-015 Could not open display.

Some hints I've found on various websites (e.g. [1]) indicate that this 
could be caused by either

1) /tmp/.X11-unix already existing (what it usually does)

2) /tmp/.X11-unix being owned by another ID (yes, usually root:system)

3) /tmp/.X11-unix not being writable (not the case, as its permissions 
are 777 or 1777)

Thus vncserver is unable to create its Unix domain socket within that 
directory, they say.

However I've found that this is not true. /tmp/.X11-unix/X<displaynum> 
gets created and so does the directory itself if it's not there yet. But 
this does not make a difference with regard to the aforementioned problem.

Starting vncserver with the "-nolisten local" option (i.e. without using 
the Unix domain socket) makes things work ok. So I propose to add this 
option as the default to the command string for Xvnc within the 
/opt/freeware/bin/vncserver script.

Any thoughts on this?

Regards,
Markus


[1] http://www.cs.columbia.edu/~crf/crf-guide/resources/software/vnc.html

-- 
Markus Alt
IBM Lab Boeblingen, Germany
al...@de...