This doesn't mean it is strictly required to reboot the system immediately after updating these packages. dbus), restarting all daemons and services by bringing the system down to single user mode (runlevel 1), and back up to the previous runlevel, is the recommended best practice. For packages that provide both services and daemons (e.g.Similarly to system reboots, Red Hat is aware that restarting services may also incur downtime for the provided service. xen, bind, cronie, cups, ntp, openssh-server), restarting the service after updating the package is sufficient to make use of the updated binaries.
It is hence recommended to reboot the system after microcode_ctl update.įor packages that provide a service (e.g. Still, it's possible that the microcode isn't taken into account until applied early during the next boot, as part of the early CPIO archive prepended to the initramfs. Package microcode_ctl applies the microcode upon update on the live system, unless it is known to have issues. This command will report whether a reboot will be needed. NOTE: Not all packages listed here are available in all versions of RHEL.īeginning in RHEL 7, yum-utils includes the needs-restarting plug-in with support for the -r, -reboothint flag.
This list is for informational use and subject to change at Red Hat's discretion. This information outlines when a reboot is required, best practice for customers following updates, and guidance on particular package update scenarios.Įach of the following packages requires a reboot in order to be fully-utilized. Such reboots do come at a cost to system uptime, however, which we know many customers are keen to avoid. This ensures that all processes and services benefit from updates to core libraries and services. Red Hat recommends that systems be rebooted after installation of an updated package.
#Switch case java rerun how to#
0 kommentar(er)
