TRANSACTIONAL-UPDAT(5)

🎀 TRANSACTIONAL-UPDAT(5) — the config files bestie 💅

okay so this is transactional-update.conf, and it lives in the transactional-update.conf manual section 5, and honestly? it's the little file that runs the whole vibe check on transactional-update(8). let's get into it ✨

---

✨ NAME ✨

transactional-update.conf — the configuration files for transactional-update, fr fr 🌸

🦋 SYNOPSIS 🦋

/etc/transactional-update.conf
/usr/etc/transactional-update.conf
/usr/etc/transactional-update.conf.d/*

like, those are the paths, memorize them, iykyk 💖

👑 DESCRIPTION 👑

so these configuration files control and define the behaviour of transactional-update(8). they are literally the main character of how it acts, no cap 🌈

the files use shell style assignments, like:

PARAMETER=value

a reference file — which is also what gets used for reading the default values — can be found in /usr/etc/transactional-update.conf. and additionally, packages may overwrite those default values by dropping files into /usr/etc/transactional-update.conf.d/. 📁

here's the tea on that directory tho: files in there get read alphabetically, and assignments in later files will overwrite previous assignments. so order matters, bestie, it's giving "read the room" 😭

and finally, admin settings in /etc/transactional-update.conf will have the highest precedence. like, that file walks in and the others move aside. periodt. 👑

---

💅 OPTIONS 💅

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

• REBOOT_METHOD — specify the reboot method to use. 🫶
  • auto — uses rebootmgr if available and active; falls back to systemd otherwise. this is the default value. also, if the option is invalid it will also be used as the fallback value. so it's the default and the safety net, iconic behaviour honestly 💜
  • kured — will inform kured (kubernetes reboot daemon) to reboot the system.
  • rebootmgr — triggers rebootmgrctl(1) to initiate a reboot or, if possible and that information is provided by zypp-boot-plugin(8) and it is allowed in tukit.conf(5), a faster soft-reboot. ⚡
  • systemd — uses systemctl(1) to initiate a reboot. this can either be a full reboot or, if possible and that information is provided by zypp-boot-plugin(8) and it is allowed in tukit.conf(5), a faster soft-reboot or kexec.
  • kexec — will use kexec to reboot the system; this will skip hardware initialization and thus boot faster than systemd.

🙈 Note — this option is deprecated, use systemd together with zypp-boot-plugin(8) to automatically detect whether kexec can be used. like, it still works, but it's giving "old money" and not in the cute way 💀

• notify — trigger the Transactional Update Notifier to inform the user about the necessary reboot. 📣
• none — ignores any reboot request, the user has to reboot the machine manually or by other means. you're on your own, bestie 🫡

• UPDATE_METHOD — 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. 🌸
  • dup — 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. ⭐
  • up — uses zypper up for updating the system; use this for regular releases like openSUSE Leap or SUSE Linux Enterprise Server / Desktop. 🍓
• ZYPPER_AUTO_IMPORT_KEYS — 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 🧚

• transactional-update(8) — go read it, bestie, it's the whole reason this file exists 💜

🌸 AUTHOR 🌸

Ignaz Forster <iforster@suse.com> — an absolute legend 👑🫶

---

okay that's the whole page!! 🎀 this was transactional-update from the transactional-update.conf manual, dated 09/04/2026, section TRANSACTIONAL-UPDAT(5) — mwah, go configure something iconic 💖✨