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? -- 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