UCS 2.4 - Univention

14 Univention Configuration Registry
• When the force option is used in setting a local variable, settings adopted from the directory service
and variables from the schedule level are overruled and the given value for the local system fixed
instead. An example:
univention-config-registry set --force mail/messagesizelimit=1000000
If a variable is set which is overwritten by a superordinate policy, a warning message is given.
14.9.2 Configuring the policy in Univention Directory Manager
When creating the policy object, Univention Configuration Registry needs to be selected. Firstly a
name must be set for the policy which is to be created, under which the variables will later be assigned to
the individual computer objects.
In addition, at least one Univention Configuration Registry variable must be configured. Firstly, the name
of the variable must be entered under Name of the new Configuration Registry variable. Clicking the
plus sign next to the input field changes the input field to Variable: NAME. The value to be set must now
be entered here.
Clicking on Ok saves the policy; alternatively, further variables can also be created.
This policy can then be assigned to a computer object. Note that the display of configured values dif-
fers from the remaining policies: the values are not display directly in Univention Directory Manager but
rather written on the assigned computer by Univention Directory Policy. The time interval used for this is
configured by the Univention Configuration Registry variable ldap/policy/cron and set at one hour as
standard.
14.10 Univention Configuration Registry in manually created packages
Configuration files can also be integrated in the Univention Configuration Registry system when creating
individual software packages for use in UCS. The complete procedure for package creation in UCS is
documented separately (see [20]).
A subdirectory with the name conffiles must be created in the directory with the package
sources. The configuration files and any subdirectories are copied here. For example, if the file
/etc/ldap/slapd.conf should be managed by Univention Configuration Registry, it is copied to
conffiles/etc/ldap/slapd.conf.
Wildcards can now be integrated into the configuration files in conffiles for the variables and any neces-
sary Python code.
In any case default values for the variables used by the respective binary package can be issued
in debian/postinst or debian/.postinst through certain settings (see
Chapter 14.5).
The line
univention-install-config-registry
284