On 12/21/16 06:27, Joe Zeff wrote: > On 12/20/2016 02:14 PM, Rick Stevens wrote: >> After a significant number of updates, it's probably be a good idea to >> reboot just to ensure you are using the latest kernel and that any >> services that were updated have been restarted. How and when that >> reboot cycle happens is completely up to you. You can ignore it all >> together if you wish. > > The package yum-utils included the program needs-restarting, which would tell you what > running programs needed to be restarted because of an update, although it didn't seem to > go so far as to tell you that you needed to reboot. Alas, there doesn't seem to be a > dnf version yet, along with several other handy yum utilities that we've lost. > ???? The OP already pointed out the existence of the dnf equivalent. It is the DNF tracer Plugin. It tells you what processes you *should* restart as well as when you *should* reboot. It does as good a job at it as "needs-restarting". The bottom line is if someone feels compelled to follow the suggestion that you *should* reboot or that "should" is equivalent to *must* then just don't apply updates until ready to take the necessary action to *fully* apply them. An additional suggestion would be for some folks to disable notifications that updates are available. I know several people that upon seeing the icon appear in their tray will drop what they are doing to update their systems as they are under the impression that failure to do so will result in dire consequences. -- You're Welcome Zachary Quinto _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
