UCS 2.4 - Univention

11.3.1 Assigning repository servers
11.3 Package maintenance
Which repository server is used for package management can be set for each UCS system. If there is
no local repository server in the UCS domain, the online repository http://apt.univention.de is
used. Otherwise the local repository server is set. This can usually be reached under the DNS alias
univention-repository.
When several repository servers are in operation, the UCS systems can distribute the load among several
repository servers. In Univention Directory Manager the repository server to be used can be entered on
the computer onjects of the UCS systems in the [Repository server] tab. As this is a policy setting, the
setting does not need to be performed on each individual computer. Policies are inherited by subordinate
objects in the directory tree.
11.3.2 Updating packages
Figure 11.1: ’Repository server’ tab
Manual updating of a UCS system is performed using the command univention-actualise as the
user root. In this, no release updates are performed, but packages are updated from the configured
repositories. univention-actualise performs a number of actions. Firstly a list of the available pack-
ages and their versions is requested from the repository server. Once the list has been compared with the
packages currently installed locally, all packages which are available in newer versions on the repository
server are downloaded and installed.
Updates can be installed automatically if the Maintenance policy is assigned to the desired systems.
Whether the update should be performed during a system start, during shutdown or at a certain time can
be set in the package maintenance policy. As package maintenance policies are inherited just like all
policies in UCS, settings for automatic updating can be made in a computer container. The settings apply
for all computer objects subordinate to the container.
It must be noted that certain packages, e.g., the kernel, are not updated by univention-actualise
241