Skip to content
No description, website, or topics provided.
C Shell M4 XSLT Makefile C++
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
dbus
etc Minor spelling corrections... Feb 15, 2017
lib
m4 First prototype for a dbus based reboot manager Nov 18, 2016
man Use python3 Aug 17, 2019
src
systemd Don't allow systemd to kill rebootmgr when attempting shutdown Sep 13, 2017
tests Add some compiler otions for better code checking Sep 6, 2019
.gitignore Continue writing documentation Feb 1, 2017
COPYING
COPYING.LIB Implement set-strategy call Nov 19, 2016
Makefile.am
NEWS
README.md
autogen.sh
config.guess First prototype for a dbus based reboot manager Nov 18, 2016
config.h.in
config.rpath
config.sub First prototype for a dbus based reboot manager Nov 18, 2016
configure.ac

README.md

rebootmgr

RebootManager is a dbus service to execute a controlled reboot after updates in a defined maintenance window.

If you updated a system with e.g. transactional updates or a kernel update was applied, you can tell rebootmgrd with rebootmgrctl, that the machine should be reboot at the next possible time. This can either be immediately, during a defined maintenance window or, to avoid that a lot of machines boot at the same time, controlled with locks and etcd.

Reboot Strategies

rebootmgr supports different strategies, when a reboot should be done:

  • instantly - reboot immediately when the signal arrives.
  • maint-window - reboot only during a specified maintenance window. If no window is specified, reboot immediately.
  • etcd-lock - acquire a lock at etcd before reboot. If a maintenance window is specified, acquire the lock only during this window.
  • best-effort - this is the default. If etcd is running, use etcd-lock. If no etcd is running, but a maintenance window is specified, use maint-window. If no maintenance window is specified, reboot immediately (instantly).
  • off - rebootmgr continues to run, but ignores all signals to reboot. Setting the strategy to off does not clear the maintenance window. If rebootmgr is enabled again, it will continue to use the old specified maintenance window.

Configuration example

File /etc/rebootmgr.conf

[rebootmgr]
window-start=3:30
window-duration=1h30m
strategy=best-effort
lock-group=default

Checking if a reboot is requested

$ sudo rebootmgrctl status
Status: Reboot not requested
You can’t perform that action at this time.