Killing VNC Process Manually

I'm looking for a way to reset the display counter for VNC to :1.

What has happened is that my server has been restarted without killing the VNC processes first and upon reboot and then starting vncserver once more with a new process it has started at :2, completely ignoring :1.

On trying to kill :1 it says: "You'll have to kill the Xtightvnc process manually".

I cannot kill this process, there is no pid files for this display to delete and the process has long gone as the server has restarted. Please can someone advise me on how to restart this count back to :1. Can anyone please help me reset these settings.

Using tightvncserver on Ubuntu 14.01

Jono_2007

Posted 2015-05-04T01:08:36.397

Reputation: 133

The server has restarted, but the process is still there? Sounds like there's a lock file of sorts left around. – Huey – 2015-05-04T05:28:27.950

I've looked through all the running processes by running 'ps aux | less' but the old processes are definitely no longer there. I do think that is the case but I don't have much idea as to where the lock files are – Jono_2007 – 2015-05-04T12:36:30.393

Have you tried vncserver -kill :2? – EternalHour – 2015-05-05T09:44:09.807

2 will kill fine but I cannot to kill 1 – Jono_2007 – 2015-05-05T14:34:55.873

Answers

Try running

ps -ef | grep vnc

to see which VNC services are running.

Bob

Posted 2015-05-04T01:08:36.397

Reputation: 36

This was the answer that led me to the answer thank you sir! I didn't realise that everytime I rebooted my server that Virtual Machine Manager would assign monitors for VNC as it saw fit to my Virtual Machines. – Jono_2007 – 2015-06-06T18:12:56.997

Can you please elaborate so that this answers the question? – Randy Cragun – 2019-12-31T23:29:00.607

The following terminal command;

$ sudo tightvncserver -kill :1

Kills the first server session and leaves the second session untouched.

Nasl

Posted 2015-05-04T01:08:36.397

Reputation: 1