vncinitconfig - VNC® Server setup utility
vncinitconfig resets VNC Server to factory defaults, and performs related auxiliary operations. ACTIONS apply to VNC Server in all modes unless otherwise stated.
vncinitconfig -install-defaults is run automatically when VNC Server is installed, and numerous files are created; examine the script for details. If you wish to subsequently edit these files, it is recommended you do so in parallel .custom files; see the header at the top of each file for more information.
Note that if you do edit the original files and subsequently run vncinitconfig, any changes are overridden but preserved in files with a .old suffix.
- Performs all the actions below except
-register-SELinux, where supported on the platform. It may be useful to perform this operation if VNC Server or any auxiliary application or file becomes corrupted.
/etc/pam.conf, depending upon the version of PAM installed, to enable system authentication using PAM. By default, the pam_unix module is referenced to query passwords against the local database store only.
If you wish to query passwords against a directory service such as LDAP, you must reference an alternative module that provides this functionality. As a convenience,
-pamadditionally lists PAM modules (such as pam_ldap.so) found on your system; you must manually create
/etc/pam.confto reference such a module.
Alternatively, for distributions such as Ubuntu with a common PAM configuration in
@include common-auth @include common-account @include common-session
For distributions such as Red Hat with a common PAM configuration in
auth include password-auth account include password-auth session include password-auth
/etc/vnc/xstartupto run a default virtual desktop environment for VNC Server in Virtual Mode. See vncserver-virtual(1).
/etc/vnc/configto specify default Xvnc options for VNC Server in Virtual Mode. See vncserver-virtual(1).
- Regenerates a private key for the root user. This key determines the identity of VNC Server in Service Mode and of the VNC Server in Virtual Mode daemon. Note you should ideally find out why the private key is missing or corrupt before performing this operation.
- Clears up old files related to licensing.
- Installs an init file for the VNC Server in Service Mode or VNC Server in Virtual Mode daemon respectively. This will be a SystemV-style init script, systemd unit file, or Solaris Service Management Facility manifest as appropriate. See vncserver-x11-serviced(1), vncserver-virtuald(1).
- Registers the VNC backend with CUPS, on platforms where the VNC backend cannot be installed directly in the CUPS directory.
- Attempts to register SELinux modules on systems with SELinux binaries. Required for the VNC Server in Service Mode and Virtual Mode daemons and printing. Note this command is not run as part of