RPMs that require reboot, etc.

Solution Unverified - Updated -


  • Some RPMs require additional post installation effort beyond that installed in the postinstall scripts.
  • In the case of the kernel it's obvious that a reboot is required.
  • Other packages include libraries that won't be fully updated until a reboot forces all running applications to reload them (libc).
  • Still other packages, like dev, can cause erratic behavior until the system is rebooted.
  • A final category of RPMs is simple ones where the target files are currently being executed on the system at the time of the update.
  • Enhance the RPM system (or Red Hat Network system) so it can provide a much better idea of what additional work is required after a particular update in order to make update scheduling more obvious.
  • The windows updater requires you to reboot after each patchset, and even enforces reboots in the middle at times for more critical patches (like kernels, etc).
  • If packages are going to require reboots or user logins/logouts after installation then admins need to know which packages these are.


  • Red Hat Satellite 5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content