REBOOTMGRD(8)

πŸ“¦ version 3.3+git20250512.b6e4e84, in opensuse-leap 16.0

✨ REBOOTMGRD(8) ✨

okay so bestie, rebootmgrd and rebootmgr.service walked into the group chat and their whole thing is: rebooting the machine during a maintenance window πŸ’… (also it's rebootmgrd from section 8 of the manual, iykyk πŸŽ€)


πŸ¦‹ SYNOPSIS

/usr/libexec/rebootmgrd [--debug | --verbose | --help | --version]

/usr/lib/systemd/system/rebootmgr.service

πŸ’– DESCRIPTION

Picture this: a whole cluster, or just a bunch of machines all doing the same task, all trying to reboot at the exact same time. Chaos 🫠. So rebootmgrd exists to keep that from happening β€” it reboots the machine following configured policies. Rue the day, scheduling drama periodt.


🧚 Reboot Strategies

rebootmgr supports various strategies for determining when a reboot should be performed, and honestly each one is a vibe of its own:

  • instantly β€” the reboot is carried out without waiting for a maintenance window. no thoughts, just reboot 😭.
  • maint-window β€” reboot only during a specific maintenance window. If no maintenance window is specified, the system reboots immediately.
  • best-effort</best-effort>** β€” this is the default setting, main character energy fr fr. If a maintenance window is specified, maint-window is used. If no maintenance window is specified, the reboot takes place immediately (instantly).
  • off β€” rebootmgr continues to run, but ignores all reboot timers that expire in the meantime. Here's the fine print: the configuration file is not updated, so this option is no longer active after a reboot. When rebootmgr is reactivated, it will continue to use the old specified maintenance window and any reboot timers that are still running will no longer be ignored. it's giving "temporary situation" πŸ’€.
  • on β€” reboots will be enabled again. Existing reboot timers will be executed again. Elapsed timers will not be restarted.

The reboot strategy can be configured via rebootmgr.conf(5) and adjusted at runtime via rebootmgrctl(1). These changes will be written to the configuration file and survive the next reboot. Except for the off strategy. 🩷


🌸 OPTIONS

  • --debug β€” log additional informations during runtime. A real reboot is not done in debug mode πŸ™ˆ (very important, bestie, no accidental sending).
  • --verbose β€” log additional informations about requested reboots. it's giving receipts ✨.
  • --help β€” display help text and exit. slay.
  • --version β€” output version information and exit. iconic.

πŸ”₯ SEE ALSO

rebootmgrctl(1), rebootmgr.conf(5), systemd.time(7) β€” the rest of the squad πŸ«ΆπŸ¦‹


πŸ‘‘ AUTHOR

Thorsten Kukuk <kukuk@suse.de> β€” literal king for this one πŸ’œ


and that's the whole page, bestie β€” no cap, every flag accounted for 🌈

rebootmgr man page, reimagined Β· source/version: rebootmgr Β· 05/12/2025 πŸŽ€ (that's the date bestie, mark your calendar and stan) 🌟

πŸ“¦ where this page comes from