Index transactional-update 4.5.0


transactional-update.conf — transactional-update configuration files




These configuration files control and define the behaviour of transactional-update(8).

The configuration files use shell style assignments, e.g. PARAMETER=value.

A reference file (also used for reading the default values) can be found in /usr/etc/transactional-update.conf. Additionally packages may overwrite these default values by putting files into /usr/etc/transactional-update.conf.d/; files in that directory will be read alphabetically, assignments in later files will overwrite previous assignments. Admin settings in /etc/transactional-update.conf will have the highest precedence.


The following options are available in the "transactional-update" section:


Specify the reboot method to use.


Uses "rebootmgr" if available and active; falls back to "systemd" otherwise.

This is the default value. If the option is invalid it will also be used as the fallback value.


Will inform kured (kubernetes reboot daemon) to reboot the system.


rebootmgrctl(1) will be triggered to initiate a reboot.


systemctl(1) will be called to initiate a reboot.


Will use kexec to reboot the system; this will skip hardware initialization and thus boot faster than "systemd".


Trigger the Transactional Update Notifier to inform the user about the necessary reboot.


Ignores any reboot request, the user has to reboot the machine manually or by other means.


Specify the zypper update method to use. This value is used for transactional-update.service(8) and in case no command is specified when calling "transactional-update".


Uses "zypper dup" for updating the system; use this on rolling release distributions like openSUSE Tumbleweed, openSUSE Kubic or the SUSE CaaS Platform.

This is the default value.


Uses "zypper up" for updating the system; use this for regular releases like openSUSE Leap or SUSE Linux Enterprise Server / Desktop.


If set to "1" GPG keys will be imported automatically for new repositories. If set to "0" updates will fail if a key is unknown. For security reasons this option is turned off ("0") by default.

See Also