UCS 2.4 - Univention

14.5 Creating new Univention Configuration Registry variables
14.5 Creating new Univention Configuration Registry variables
A new variable can be registered with univention-config-registry and the parameter set. The
variable can be given any name consisting exclusively of lowercase letters, full stops, figures, hyphens
and forward slashes. If the newly created Univention Configuration Registry variable is to be automatically
used in configuration files it should be registered (see Chapter 14.7).
# univention-config-registry set test/variable=neu
Create test/variable
A conditional setting of variables is also possible. For example, if a value should only be saved in a
Univention Configuration Registry variable when the variable is empty, this can be done by entering a
question mark instead of the equals sign when assigning values.
univention-config-registry set dns/forwarder1?192.168.0.2
In this example, the variable dns/forwarder1 is only set to the value 192.168.0.2 when it was previously
empty. When the variable already contains a value, this is not changed.
When setting and changing Univention Configuration Registry variables, numerous variables can be en-
tered in one execution.
14.6 Deleting Univention Configuration Registry variables
The parameter unset is used to delete a variable. The following example deletes the variable dns/for-
warder2. It is also possible here to specify several variables to be deleted.
univention-config-registry unset dns/forwarder2
When deleting a variable, univention-config-registry displays which files are affected by the change and
rewritten.
14.7 Registering Univention Configuration Registry variables
The Univention Configuration Registry system guarantees the regeneration of the configuration files for
which a variable is registered when a change is made to this variable. This is done using Univention
Configuration Registry templates. Essentially, a Univention Configuration Registry template is a copy of
the original configuration file in which the lines in which the value of a Univention Configuration Registry
variable are entered are partially replaced with program code.
The Univention Configuration Registry variables used in the configuration files are registered in info files
in /etc/univention/templates/info which are named after the package name with the file ending
.info. An example for the package univention-dhcp:
Type: file
File: etc/dhcp3/dhcpd.conf
Variables: ldap/base
Variables: dhcpd/ldap/base
281