HOST_STATUS_COMMAND also prints freebsd-version -k (installed kernel) and -r (running kernel) where freebsd-version exists. get_host_status reports the host as needing a reboot when the two differ ("kernel X installed, Y running") and as not needing one when they match. Other systems are unchanged.
The test fixture is the output recorded on a FreeBSD 15.1 host before its update.
Version 4.1.0. napalm-bsd uses this through HostStatusMixin (NetOrk/netork#799).
`HOST_STATUS_COMMAND` also prints `freebsd-version -k` (installed kernel) and `-r` (running kernel) where `freebsd-version` exists. `get_host_status` reports the host as needing a reboot when the two differ ("kernel X installed, Y running") and as not needing one when they match. Other systems are unchanged.
The test fixture is the output recorded on a FreeBSD 15.1 host before its update.
Version 4.1.0. napalm-bsd uses this through `HostStatusMixin` (NetOrk/netork#799).
HOST_STATUS_COMMAND also prints freebsd-version -k and -r where
freebsd-version exists. When the two differ, a kernel update was installed
and is not running yet, so the host needs a reboot. When they match, it does
not.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
HOST_STATUS_COMMANDalso printsfreebsd-version -k(installed kernel) and-r(running kernel) wherefreebsd-versionexists.get_host_statusreports the host as needing a reboot when the two differ ("kernel X installed, Y running") and as not needing one when they match. Other systems are unchanged.The test fixture is the output recorded on a FreeBSD 15.1 host before its update.
Version 4.1.0. napalm-bsd uses this through
HostStatusMixin(NetOrk/netork#799).