On Thu, 2017-09-07 at 21:53 +0800, Ed Greshko wrote: > On 09/07/2017 09:32 PM, Wolfgang Pfeiffer wrote: > > See? "The safest possible way to update a Fedora system is to use > > the > > ‘offline updates’ mechanism." > > > > That's why I started the thread. Again: I use dnf, not the GNOME > > update > > mechanism, but from how I understand A. Williamsen, this might also > > apply to package updates via dnf and the reboot following on that > > ... > > > Yes, that is the "safest" path. > > The best thing to do after an update via dnf is to run "dnf needs- > restarting". Wow, that looks like a really powerful tool: I didn't even know about it. Thanks a lot for letting me know: might save me quite some time ... I really will need to have a look at the rest of the installed dnf.plugin.* tools ... > This will give you a list of processes that could potentially be > impacted by the last update by, for example, some libraries being > updated. > > Depending on what you find, you may just need to logout/login to > restart the > processes. Or, you may need to restart some daemon using "systemctl > restart whatever". > > There is no definitive answer to the question. That's actually what I was thinking, too. But I simply don't know too much about Fedora so far to be sure about it ... > I've the habit of not rebooting or logging out. Most of the time to > no ill effect. Other times, after a while, I may find some odd > behaviors. So, I'll logout/login and if all is OK, continue. If the > oddities continue, I'll reboot. Makes sense, yes ... > > I've never run into a situation where a corruption occurred causing a > permanent damage to my system. Sounds good ... :) As I said: For an update I - meantime - always try to log out of the X environment and then start the upgrade process on a VT - I think this is a good idea. Again: thanks again for mentioning the "needs-restarting" plugin ... Regards Wolfgang > _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
