Xvnc & xstartup
cbeerse "at" hiscom.nl
Mon Jun 10 16:15:02 2002
> -----Original Message-----
> From: Lee Allen [mailto:lee "at" leadtec.com]
> When Xvnc is run in -inetd mode, is there some reason it does
> not execute xstartup or .xinitrc ?
Yes, -inetd is to be used from inetd (or xinetd or tcpserve or stuf like
that) Hence it get started without a real user.
Actually, Xvnc never starts xstartup or .xinitrc. It's your startup script
that starts both Xvnc and xstartup or .xiinitrc. vncserver is that script
for most of you, have a look and try to read what happens.
> I realize it can be configured to use XDMCP, I'm just
> wondering why this simpler mechanism is not utilized.
It is used as described above. THe reason is the order in which things
happen: is it first login and then windows startup, then the .xinitrc and
xstartup scripts can be used. Is it first windows startup and then login,
it's xdmcp that starts the login.
On most linux machines, you can replay this by putting the machine in
runlevel 3. Then, at the prompt type `startx` or `xstart` and see the
windows come to you. If you don't start the windows but start vncserver,
don't be surprised it gives you display :0.
Just did the next on my (RH 7.3) linux machine:
reboot to runlevel 3:
edit /etc/inittab and changed the default runlevel from 5 to 3
At the text-console, login as a normal user
This gives me the vncserver with display :0 at a unix machine
then to have X windows at the console:
startx -- :1
Ending with the reverse world: display:0 is in vnc, display:1 is at the