You shouldn't have to do anything with the XServer configuration.
You must edit /etc/services and add something like:
vnc 5950/tcp
This tells inetd which port to listen on and the name of the service. Once a
request comes in on that port, inetd creates a new connection of the type
specified in the inetd.conf file (stream for vnc). It then exec's a new
process using the command line given in the inetd.conf file. The new process
is also created as the user specified on the line defined in inetd.conf. If
set up correctly, the inetd.conf line would look something like:
vnc stream tcp nowait nobody /usr/local/bin/Xvnc Xvnc -inetd -once -query
localhost
This configuration is the most basic. If you want more command line options,
then you may need to do some things with a shell script.
Also, if you have problems, then change "nobody" to "root" to make sure that
Xvnc is configured correctly. Using root will allow you ignore file
permission issues in the beginning for debug purposes. If you have all the
file permissions setup correctly, you can go back to using "nobody" and it
will still work. The permissions I had to change were to allow execute
permissions on the Xvnc files. I just did the following:
chmod 755 /usr/local/bin/Xvnc
I then did:
chmod 01777 /tmp/.X11-unix
There is a FAQ entry on this, but I do not know what this directory is used
for except that there are temp files created here. That should be it. I
rebooted my machine and then I can connect to <hostname>:50 using the
vncviewer. Inetd takes care of the rest. There is a way to reinitialize
inetd without rebooting, but I can't remember what it is and haven't spent the
time to figure it out again.
Taking it one step further, if you connect remotely from machines with varying
resolution capabilities, then you can follow the following pattern:
#/etc/services
vnc-640x480x16 5950/tcp
vnc-800x600x16 5951/tcp
vnc-1024x768x16 5952/tcp
vnc-1280x1024x16 5953/tcp
#/etc/inetd.conf
vnc-640x480x16 stream tcp nowait nobody /opt/vnc/Xvnc Xvnc -inetd -once
-query localhost -geometry 640x480 -depth 16
vnc-800x600x16 stream tcp nowait nobody /opt/vnc/Xvnc Xvnc -inetd -once
-query localhost -geometry 800x600 -depth 16
vnc-1024x768x16 stream tcp nowait nobody /opt/vnc/Xvnc Xvnc -inetd -once
-query localhost -geometry 1024x768 -depth 16
vnc-1280x1024x16 stream tcp nowait nobody /opt/vnc/Xvnc Xvnc -inetd -once
-query localhost -geometry 1280x1024 -depth 16
Make sure the name of the vnc service is identical in both files. To connect
you then specify <hostname>:50 or <hostname:51>. The VNC viewer client adds
the display number (50) to port 5900 to get 5950 and so forth. You can set up
any number of ports for any number of resolutions and color depths. Again,
make sure that all specific files have the correct permissions. I believe
that is all. If there are problems let me know and I will do the best I can
to help. I am still shaking the rust off of my Unix/Linux skills and am still
muddling through a lot of this myself.
I found that Netscape and Java apps DO NOT LIKE THE 32 BIT COLOR DEPTH
setting. So I added entries for 8 (ports 595x),16 (ports 596x), 24 (ports
597x), and 32 (ports 598x) bit color depths. I can now connect to 5950 and get
640x480x8 or connect to 5984 and get 1600x1200x32. I am a little anal and was
tired of changing inetd.conf and services to determine the best
color/resolution I could use for all my apps so I added them all. If I have a
problem, I just reconnect to a lower (or higher) color depth and see if I get
the same problem. I am now using mine at 5973 (1280x1024x24) and that seems
to be the best for my everyday uses.
Additionally on some versions of Linux, the xdm (kdm or whatever) ships with
XDMCP disabled, so you must enable it through the xdm-config by commenting out
the line:
'DisplayManager.requestPort: 0'
usually by placing a '!' in front of it. My SuSE Linux distribution has the
following path for the xdm config file:
/usr/X11R6/lib/X11/xdm/xdm-config
The symptom I experienced was that I could attach to the VNC server, but all I
would get was a grey screen with an X mouse cursor. Other people have posted
that if this happened, then your xdm was not running. However, mine was
running and I spent a day (learning) figuring out if my xdm was running and
was running in daemon mode and if XDMCP was enabled. I discovered the XDMCP
thing in search through the mailing list archives.
Hope this helps.
Jeff
>>> [EMAIL PROTECTED] 03/08/01 05:50AM >>>
Hi... sorry if this question gets asked alot....
My problem is thus:
Having setup iXvnc and put an entry into my /ets/X11/xdm/Xservers (which
works when invoked directly: in my case ipaddress:01)... however no matter
what I do I cant get iXvnc to invoke it....
I've set the broadcast option in my inetd.conf, but it still wont work...
Does anyone think thay can help????
Much appriciated..
Thanx...
See Ya :)
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
