On 09/07/2017 11:46 PM, Patrick O'Callaghan wrote: > On Thu, 2017-09-07 at 21:53 +0800, Ed Greshko wrote: >> The best thing to do after an update via dnf is to run "dnf needs-restarting". This >> will give you a list of processes that could potentially be impacted by the last >> update by, for example, some libraries being updated. > AFAIK this has now been deprecated in favour of 'tracer' (standalone > command). Also the dnf.plugin.tracer plugin. > 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. -- Fedora Users List - The place to go to speculate endlessly
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
