UCS 2.4 - Univention

14.8 Regeneration of configuration files
configuration files. When packages are updated, a check is performed for whether any changes have
been made to the configuration files. If configuration files are no longer there in the form in which they
were delivered, they will not be overwritten. Instead a new version will be created in the same directory
with the ending .debian.dpkg-new. If changes are to be made on the Univention Configuration Reg-
istry templates, these templates are also not overwritten during the update and are instead resaved in
the same directory with the ending .dpkg-new or .dpkg-dist. Corresponding notes are written in the
/var/log/univention/actualise.log log file.
14.8 Regeneration of configuration files
The command
univention-config-registry commit
is used to regenerate configuration files from their templates, which may be necessary, for example, if a
change is made to a configuration file as a test or the corresponding Univention Configuration Registry
template has been edited.
If no file name is given when running univention-config-registry, all of the files managed by Univention
Configuration Registry will be regenerated from the templates. It is, however, not generally necessary to
regenerate all the configuration files.
The command
univention-config-registry commit /etc/samba/smb.conf
is used to rewrite the configuration file for the Samba service, for example.
14.9 Policy-based configuration
14.9.1 Overview
Part of the settings stored in Univention Configuration Registry are system-specific (e.g., the computer
name); many other settings can, however, be used on more then one computer. To automate the distribu-
tion of the settings, you can configure the Univention Configuration Registry variables using a policy in the
directory service. General information on policies can be found in Chapter4.5.11.
The evaluation of the Univention Configuration Registry variables on a UCS system comprises four stages:
• First the local Univention Configuration Registry variables are evaluated.
• The local variables are overruled by policy variables which are usually sourced from the directory
service using unvention-policy-result.
• The schedule option is used to set local variables which are only intended to apply for a certain
period of time. This level of the Univention Configuration Registry is reserved for local settings which
are automated by time-controlled mechanisms in Univention Corporate Server.
283