One more time, StartingVNC at boot in linux

David Colliver david.colliver "at"
Fri, 11 Jan 2002 12:42:38 +0000


Thanks for your help with this. I have done the suggested items and now can
connect, except, I have a grey screen with a cross on it. Nothing else. no
left,middle or right click available.

I would like to at least have a login screen.

When I have nobody in the inetd.conf, is that just a text value? (The value
came on the title of the VNC window). I changed this to a logon name, but it
still doesn't get my desktop.

Another question, I assume everyone will have the same VNC  login password
just to connect to the remote VNC. Is there anyway to configure this to use
different passwords. This isn't essential to me, but would be nice.

It seems like when you play with things on Linux, you need a lot of
patience. I would like to see Linux as a desktop operating system, but until
the configuration issues are made easier, I don't think it is likely to
happen. Only people with knowledge of computer systems and patience, and
knowledge of where to get help can really use Linux.

David Colliver.
All I ask is a chance to prove that money can't make me happy.

Collectible dolls from
Web design? is the answer.
Tips, tricks and articles for programmers of all languages on
Planning a wedding?
Advertise your car for free on

----- Original Message -----
From: <barnowl "at">
To: "vnc" <vnc-list "at">
Sent: Thursday, January 10, 2002 4:46 AM
Subject: One more time, StartingVNC at boot in linux

> Instead of psting this in about 4 threads, I will answer teh question
about load vnc at boot the VNC standard way. Why do I call it the VNC
standard way? Because this the method built in to the program. The -inetd
option allows you configure inetd/xinetd to run VNC at boot. The big
advantage here is that it also allows for remote login of ANY account on the
> From the orignal website of  iXVNC:
> "New entries are required in /etc/services and /etc/inetd.conf.
> /etc/services
> In this file the new services must be defined: service-name
port-number/protocol . In our case we want to give users several options
about geometry's and depths so my file has this lines (you may want just
> vnc-640x480x8 5950/tcp
> vnc-800x600x8 5951/tcp
> vnc-800x600x16 5952/tcp
> On the client side this means displays :50 :51 and :52. The display number
used by Xvnc won't be the same; with -inetd option an available display
number will be searched and used.
> /etc/inetd.conf
> In this file you must add the lines to launch Xvnc, in my case the basic
options are:
> vnc-640x480x8 stream tcp nowait nobody /usr/local/bin/Xvnc
Xvnc -inetd -broadcast -once -geometry 640x480 -depth 8
> vnc-800x600x8 stream tcp nowait nobody /usr/local/bin/Xvnc
Xvnc -inetd -broadcast -once -geometry 800x600 -depth 8
> vnc-800x600x16 stream tcp nowait nobody /usr/local/bin/Xvnc
Xvnc -inetd -broadcast -once -geometry 800x600 -depth 16
> You must add other command line options required for your local
configuration, namely -fp.
> As you can see Xvnc will run as nobody (check if that's ok for your local
configuration). Any number of clients may connect to :50 :51 or :52, inetd
will launch a Xvnc for each. You may use any Xvnc options (some systems may
restrict the number of command args in inetd.conf) but don't
forget -inetd -broadcast -once, of course -broadcast can be replaced
by -query {hostname}.
> After changing these files you must send a HUP signal to inetd process (or
> xinetd works much the same. Except that each option is on its own line.
this should at least get most ppl up and running.
> Evan Hisey
> P.S.  KDE sometimes has trouble running in multiple instances as the same
user. Gnome has a habit of being off color.
> ---------------------------------------------------------------------
> To unsubscribe, mail majordomo "at" with the line:
> 'unsubscribe vnc-list' in the message BODY
> See also:
> ---------------------------------------------------------------------
To download your own free RevilloC mailserver, visit
To unsubscribe, mail majordomo "at" with the line:
'unsubscribe vnc-list' in the message BODY
See also: