On Fri, 2017-09-08 at 01:16 +0100, Patrick O'Callaghan wrote: > On Fri, 2017-09-08 at 07:14 +0800, Ed Greshko wrote: > > [ ... ] > > > > I rarely use needs-restarting. On the issue of tracer I actually > > tried it and hate > > it more than needs-restarting. > > > > As Matthew pointed out, needs-restarting is rather slow. But, at > > least you can elect > > to run it. With the tracer plugin it runs after every successful > > dnf run and it is > > no faster than needs-restarting. Additionally, I found it > > interfered with the akmod > > process update of nVidia drivers when the kernel was updated. > > True that it's no faster, but it does have options that can give more > information and hints about what to do. Not in all cases though. It > will often say "restart foo manually" and you have to investigate how > to do that because it doesn't know, which can be a challenge when foo > is some daemon you aren't familiar with and was originally started at > boot time. Exactly: It can be difficult to see which services need to be restarted, and how they need to be restarted properly (order of restarting might even be relevant) ... I'm more and more wondering why Fedora users after an upgrade are supposed to test by **themselves** via the various plugins whether there are services that need to be restarted in the running system, or whether there is even a full reboot needed. That whole testing of services and whether their restart/reload is needed, then actually restarting them is something the dnf installer might be able to do by itself: Inform the user - maybe at the end of or during an upgrade - which services need a restart: dnf: "Shall we restart foo now: Yes or No, and if No: here's how you can do it manually ...." Or if a reboot is required: tell the users ... That whole procedure looks actually like a no-brainer ... What did I miss? ... Wolfgang _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
