NAME

vncserver-x11-serviced - VNC® Server in Service Mode  

SYNOPSIS

vncserver-x11-serviced [OPTION...] [COMMAND]  

DESCRIPTION

vncserver-x11-serviced is a daemon that starts VNC Server in Service Mode in order to remote the console of a computer to connected VNC Viewers. This may be the desktop of the currently logged-on user, or else the login screen. The daemon can be started manually, but is designed to be started automatically at system boot time; see STARTING THE DAEMON. Note that the daemon survives a restart of the X server.

When the daemon starts, it immediately runs vncserver-x11 as the root user; see vncserver-x11(1). This means that to work with VNC Server in Service Mode you actually interact with a privileged instance of VNC Server in User Mode; see VNC CONFIGURATION FILES.

By default, a VNC Viewer can connect if VNC Server has:

o
An Enterprise or a Personal license by supplying the system credentials of either the root user or of a member of the admin group. Specify the Permissions VNC parameter to widen or restrict access to other users or groups.
o
A Free license by supplying a password specific to VNC; see vncpasswd(1).

Note that vncserver-x11-serviced consumes one desktop from your license, as the root user.  

COMMANDS

Applying a command to vncserver-x11-serviced performs an auxiliary operation instead of starting the daemon.

To see a list of valid commands, run vncserver-x11-serviced -help.  

OPTIONS

Options are VNC parameters, used to configure the daemon, and also the following:
-fg
Runs in the foreground (not as a daemon), which may be useful for troubleshooting.

To see a list of valid VNC parameters, run vncserver-x11-serviced -help.  

VNC CONFIGURATION FILES

VNC parameters can be specified as command line OPTIONS, but preferably in VNC configuration files. VNC configuration files are available for:
o
All VNC applications, or just the daemon
o
All users of the computer, or just the root user
o
Policy, in order to lock down the daemon (Enterprise license required)

When the daemon starts, VNC parameters are applied in the following order:

1
System-wide VNC configuration files
2
Per-user VNC configuration files
3
Command line OPTIONS
4
Policy VNC configuration files

This means that a particular VNC parameter specified at the command line overrides the same parameter specified in a per-user or in a system-wide VNC configuration file, but is itself overridden by the same parameter specified in a policy VNC configuration file. Policy cannot be changed by users.

Note there is a disadvantage to specifying VNC parameters at the command line: parameters cannot be reloaded while the daemon is running. VNC configuration files can be reloaded, however, which means that the daemon can be reconfigured without downtime.

For a list of the VNC configuration files available for the daemon, and for detailed explanations of individual VNC parameters, start with
http://www.realvnc.com/products/vnc/documentation/latest/guides/user/am1082101.html#Ram86607

Note that an equivalent set of VNC configuration files is available for the instance of vncserver-x11 started by the daemon. To configure key activity such as connectivity, users, permissions, logging, and the session itself, edit VNC configuration files for vncserver-x11 owned by the root user.  

DISPLAY MANAGER

Some display managers do not allow connections when the computer is at the login screen, for example dtlogin under HP-UX, AIX, and Solaris up to v10. You may need to uncomment the following command, or add it to /usr/dt/config/Xconfig:
Dtlogin*grabServer: False
Note that this change means any program can connect to the X server at the login screen (subject to the normal X authorization rules).  

USER INTERFACE

Under some window managers, VNC Server is unable to determine the identity of the current desktop owner, and consequently the VNC Server user interface (a status dialog and icon) cannot be displayed automatically. If this is the case, run the following command (as the desktop owner, not as root):
vncserver-x11 -serviceui
It may be convenient to include this in a user's .xstartup file (or appropriate startup file for the desktop environment).  

STARTING THE DAEMON

A suitable init file should have been installed with VNC Server; see vncinitconfig(1). To start the daemon manually:
o
For a Linux distribution using systemd, run systemctl start vncserver-x11-serviced.service
o
For a Linux distribution using initd, run /etc/init.d/vncserver-x11-serviced start
o
For a Debian-compatible Linux distribution using initd, (alternatively) run service vncserver-x11-serviced start

To start the daemon automatically at system boot time, use the appropriate configuration tool for your system:

o
For a Linux distribution using systemd, run systemctl enable vncserver-x11-serviced.service
o
For a Debian-compatible Linux distribution using initd, run update-rc.d vncserver-x11-serviced defaults
o
For a Red Hat-compatible Linux distribution using initd, run chkconfig --add vncserver-x11-serviced

For UNIX systems, please consult the appropriate startup script documentation.  

LOGGING

By default, vncserver-x11-serviced logs basic activity to file at /var/log/vncserver-x11.log.

To change the log quality, quantity, or destination, specify the Log, LogDir, and LogFile VNC parameters.  

SEE ALSO

vncserver-x11(1), vnclicense(1), vncinitconfig(1), vncpasswd(1), vncviewer(1)  

AUTHOR

Copyright © 2002-2014 RealVNC Ltd.

VNC is a registered trademark of RealVNC Ltd. in the U.S. and in other countries. Protected by UK patent 2481870.

http://www.realvnc.com