systemctl .service file for vncserver under CentOS 7.7

People can do almost everything vis ssh under Linux, no exception for CentOS. But in some cases, using a X Windows improves efficiency greatly.

Tiger VNC server is a good server end package for VNC protocal under CentOS.
Tonight, just an hour ago, I encountered a disaster due to an unprofessional systemctl script privided by Tiger VNC server devolopers.

I’m tired so I shall not record the details.
If you are suffering problems while you are deploying autostart VNC server via systemctl, like:

  1. New main PID <pid> does not belong to service, and PID file is not owned by root. Refusing.;
  2. Enabled multiple vnc ports for no reason;
  3. Can not input password when the vnc client in locked screen;

Just try a .service file as fllow:
Do !NOT! forget to change USERNAME to your own user.

Description=Remote desktop service (VNC)


# Clean any existing files in /tmp/.X11-unix environment
ExecStartPre=/sbin/runuser -l <USERNAME> -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
ExecStart=/sbin/runuser -l <USERNAME> -c "/usr/bin/vncserver :1"
ExecStartPost=/bin/sh -c '/usr/bin/cat /home/<USERNAME>/.vnc/ > /tmp/'
ExecStop=/sbin/runuser -l <USERNAME> -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'


Tag: none

Only one comment

  1. Gianluca Gianluca

    Thanks a lot for your precious help!
    I have modified the script to work with multiple users or multiple connections, as follows

    ExecStart=/sbin/runuser -l -c "/usr/bin/vncserver %i -geometry 1440x900 -localhost -nolisten tcp"
    ExecStartPost=/bin/sh -c '/usr/bin/cat /home//.vnc/ > /tmp/'

    where I included the optional directives -localhost, -geometry and -nolisten.

Leave a new comment