John Aldrich wrote:
I made the mistake of leaving a full-screen VNC session going from my wife's
Windows ME box to my linux box. She couldn't figure out how to get back to
Windows, so she rebooted her box. Now, my system thinks that there's a :1
session going somewhere, but I can't seem to find the lock or the PID file.
I've looked in my ~/.vnc folder, renamed the .vnc folder to .vnc-old and made
a new .vnc folder, and copied the relevant files over, rebooted my box (I
needed to anyway, to use the new kernel I installed via up2date awhile back)
and still, every time I try to start a new VNC session, I get it starting
on :2.
Any ideas on how to get the new session started on :1 again? There are no vnc
server sessions currently running, I checked. I *did* have a stale .pid file,
only visible by root, but it's gone now.
HELP! I'd really like to get my :1 session back, since that's the session I
tunnel to from my Win2k box at work. :-)
Thanks
John
Have you tried to start the server using #vncserver :1 ?
You should be able to kill the other using #vncserver -kill :2
Marcus
