![]() ![]() This setup uses the display manager to authenticate users and login, so there is no need for VNC passwords. One can use systemd socket activation in combination with XDMCP to automatically spawn VNC servers for each user who attempts to login, so there is no need to set up one server/port per user. Running Xvnc with XDMCP for on demand sessions ![]() The ExecStartPre line waits for Xorg to be started by $ -SecurityTypes=TLSPlain. ~/.config/systemd/user/rvice ĮxecStartPre=/bin/sh -c 'while ! pgrep -U "$USER" Xorg do sleep 2 done'ĮxecStart=/usr/bin/x0vncserver -rfbauth %h/.vnc/passwd In order to have a VNC Server running x0vncserver, which is the easiest way for most users to quickly have remote access to the current desktop, create a systemd unit as follows replacing the user and the options with the desired ones: etc/systemd/system/rvice ĭescription=Remote desktop service (VNC) for :0 displayĮnvironment=XAUTHORITY=/var/run/lightdm/root/:0ĮxecStart=x0vncserver -display :0 -rfbauth ~/.vnc/passwdĪs this is a system unit, -rfbauth ~/.vnc/passwd refers to /root/.vnc/passwd LightDM is used for the example below, but it should be possible to adapt it to other display managers by modifying the XAUTHORITY variable. The service will be relaunched automatically every time an user logs off of their session. This option will allow the users to access the current display, including the login screen provided by your display manager. See: Issue #529.Ī simple way to start x0vncserver is adding a line in one of the xprofile files such as:
0 Comments
Leave a Reply. |