Is it possible to start vncserver on :0
when its already started on :1
without having to reboot the system?
System details:
Gnome desktop manager
[root@server ~]# uname -a
Linux server.com 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed May 15 10:48:38 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 6.4 (Santiago)
Running on :1
[root@server ~]# vncserver :1
A VNC server is already running as :1
Want to use :0
instead but getting the following error:
[root@server ~]# vncserver :0
WARNING: The first attempt to start Xvnc failed, possibly because the font
catalog is not properly configured. Attempting to determine an appropriate
font path for this system and restart Xvnc using that font path ...
Could not start Xvnc.
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
List of files under /tmp
[root@server ~]# ls /tmp/.
./ ../ .esd-0/ .esd-500/ .ICE-unix/ .X11-unix/
vncserver tries to create a full window manager and all that, and your :0 likely already has those things going for it.
What you are looking for is using "x11vnc." I believe it will give you the desired effect, even without the :0 argument. There is a distinct yum-package, "x11vnc."