Starting VNCserver on screen #1 everytime

the_reen · 02-18-2005, 06:24 PM

Hello!

I have problem with starting Vncserver in my SuSE 9.2 distribution on the same screen after reboot or power down.

The problem is in file that vncserver makes on launch, in tmp directory (/tmp/.X11-unix). When the file is there, I can't run vncserver on the same screen number, vnc automatically launches on the next one.

How can I override it that everytime I start vnc it will run on the same screen, for example #1? Maybe delete the file before launch? Any other way?

acid_kewpie · 02-19-2005, 03:51 PM

how are you controlling the stopping and starting? if you're manually starting it in an informal script and then just shutting down without stop VNC, then naturally that lock file won't be taken care off. if you don't already have one, i'd suggest creating an rc.d script to both stop and start the service. with a stop of the service on close the file should be cleanly removed. alternatively ( or additionally) you can modify the startup script to run an rm on the potential lock file before runnign vncserver.

if you've not made a startup sctrip before, it's normally quite easy. just find an existing on in /etc/init.d/rc.d or a similar location on your system that is very basic, and copy and alter a few lines to suit.

the_reen · 02-19-2005, 07:38 PM

Hey, thx for quick help.

I'm running the vncserver via vnc script (/var/bin/X11/vncserver), looks like I see the problem in it:

Code:

# If the unix domain socket exists then use that (DISPLAY=:n) otherwise use
# TCP (DISPLAY=host:n)

if (-e "/tmp/.X11-unix/X$displayNumber") {
    $ENV{DISPLAY}= ":$displayNumber";
} else {
    $ENV{DISPLAY}= "$host:$displayNumber";
}
$ENV{VNCDESKTOP}= $desktopName;

system("$xstartup >> " . &quotedString($desktopLog) . " 2>&1 &");

exit;

Can I delete this part?

acid_kewpie · 02-19-2005, 07:44 PM

well no, as that's the official controlling script, after all, that lockfile is there for a reason. it's not unreasonable to blindly try to delete the file on a boot, as clearly it won't already be running, but editing the actual vncserver wrapper script isn't a great idea.