UCS 2.4 - Univention

14 Univention Configuration Registry
Variables: ldap/server/name
Variables: dhcpd/enable
Type: file
File: etc/init.d/dhcp3-server
The templates for all configuration files managed with Univention Configuration Registry can be
found in the /etc/univention/templates/files. The path to the templates is the abso-
lute path to the configuration file with the prefixed path to the template directory. For ex-
ample, the template for the /etc/dhcp3/dhcpd.conf configuration file can be found under
/etc/univention/templates/files/etc/dhcp3/dhcpd.conf.
The templates contain wildcards for the variables used in the registration. If the value of a variable is
changed, Univention Configuration Registry reads the template and replaces the wildcard with the corre-
sponding variable value before rewriting the configuration file.
The following excerpt serves as an example of a line with wildcards from the template for the file
/etc/ssh/sshd_config. The name of the Univention Configuration Registry variable framed by the
string @%@ represents the wildcard.
X11Forwarding @%@sshd/xforwarding@%@
The original configuration file is overwritten when a registered Univention Configuration Registry variable
is changed, which means that manual changes previously made to the configuration file will be lost. If
these changes are to be permanent, they must be made to the template. Once the template has been
changed, the configuration file needs to be rewritten (see Chapter 14.8).
Attention:
For the configuration files to be processed correctly by Univention Configuration Registry they must be
in UNIX format. If configuration files are edited in DOS or Windows, for example, control characters are
inserted to indicate line breaks, which can disrupt the way Univention Configuration Registry uses the file.
The string @!@ can also be used alongside the string @%@ for individual Univention Configuration Reg-
istry variables. It is used to mark Python codes embedded in blocks. The Python code is also executed
when a registered Univention Configuration Registry variable is changed. For example, these blocks can
be used to set it so that when a parameter is changed via a variable, further dependent settings in are au-
tomatically adopted in the configuration file. The following code sequence configures for example network
settings using the Univention Configuration Registry settings:
@!@
for i in range(0,4):
if baseConfig[’interfaces/eth%s/address’ % i]:
print ’%s\tunivention-directory-manager.%s univention-directory-manager’ % \
(baseConfig[’interfaces/eth%s/address’ % i],baseConfig[’domainname’])
@!@
If new Python code is entered into the templates or the existing code changed in such a way that it requires
additional or different variable, the .info files in /etc/univention/templates/info will need to be
expanded or changed accordingly (see Chapter 14.10).
Attention:
Univention Configuration Registry templates are included in the corresponding software packages as
282