using xinetd to start Xvnc
Fri Apr 18 18:01:01 2003
Christian J. Miller said:
> It now appears that there is no way to display such a desktop more than
Correct, this is a consequence of using xinetd to start the server. You
also loose the ability to have persistant connections because xinetd kills
the server when you disconnect.
> For contrast, if I use vnc server on any or my windoze boxes, I
> can vnc view the desktop from any place on the network.
For the record comparing the Linux VNC server and MS Windows VNC server
doesn't make sense. They are really two completely different servers that
just happen to speak the same language.
> I expect I
> should be able to fire up vncviewer and point it to the equivalent of
> localhost.localdomain:2 and have it work eg: vncviewer
> localhost.localdomain:2,but I get an error: "vncviewer:
> ConnectToTcpAddr: connect: Connection refused /nUnable to connect to VNC
This is because you are using xinetd to start the server. Quoting the Xvnc
This significantly changes Xvnc's behaviour so that it can be launched
from inetd. Instead of listening for TCP connections it uses its standard
input and standard output as a connection to the VNC viewer."
Xinetd starts the vncserver and communitates with it over standard input
and output. Xinetd actually does the network communication.
> I did run vncpasswrd for the user that currently has the
> desktop on localhost.localdomain:2.0
> Can anybody tell me the changes that will let me vncview a desktop that
> has been started with xinetd on, for example, a second machine?
> Life is a journey, not a destination ...
Don't start it with xinetd. Either start a session for the specific user
at boot with scripts, or start the session when you need it from a console
(or telnet, ssh, xterm, whatever).