David Bolt wrote:
On Tue, 7 Apr 2009, David C. Rankin wrote:-
Listmates,
After fiddling with both TightVNC and Xnest, I found that after making a connection with Xnest and exiting, I was then unable to start vncserver on display :1 on the same machine forcing me to start vncserver on display :2. The original Xnest session was ended by a ^c on the remote machine. I have grepped the running processes for X and vnc, but cannot find any process on display :1 to kill. Even after restarting xdm, something still has display 1 taken.
23:49 ecstasy:~> vncserver -geometry 1280x800 -depth 16 :1 A VNC server is already running as :1
What do I do to find out what it is and kill it?
If there really isn't a server listening on :1, in my case it's always Xvnc, what's most likely happened is either the socket or lock file has been left behind. You can remove them using:
rm /tmp/.X11-unix/X1 /tmp/.X1-lock -f
Regards, David Bolt
Thanks David, Rajko, I'll check the locks, but really there wasn't anything else listening. I suspect that after Xnest has run, even after it is killed, the Xserver still considers :1 as belonging to it. So when vncserver is started, it won't violate the X hold on :1, and wants to set itself up on :2. Next time it happens, I'll search for the locks, becausee I'm fairly confident that the lock will still be there from the Xnest session. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org