On Thu, 2018-06-07 at 00:55 +0800, Ed Greshko wrote:
On 06/06/18 23:47, Patrick O'Callaghan wrote:
> On Wed, 2018-06-06 at 14:44 +0200, Wolfgang Pfeiffer wrote:
> > On Wed, Jun 06, 2018 at 12:29:02AM +0100, Patrick O'Callaghan wrote:
> > > On Tue, 2018-06-05 at 18:39 +0200, Wolfgang Pfeiffer wrote:
> > > > And for those not so happy with tracer, there's also another
tool:
> > > > dnf.plugin.needs_restarting ("dnf needs-restarting")
> > >
> > > AFAIK tracer is a rewritten and expanded version of needs-restarting.
> >
> > Ed Greshko a little earler in this thread was writing about rpm
> > database lockings that might be related to tracer. And you also
> > weren't sure in your answer about the issue, IIUC. That was the main
> > reason I mentioned "dnf needs-restarting" .. Just in case someone is
> > trying to avoid usage of tracer at any cost ... :)
> >
> > And no: I do not have specific knowledge about "dnf
needs-restarting":
> > just used it a few times ..
>
> IIRC needs-restarting also locks the RPM database, but otherwise I'm
> not really clear on the differences, except that apparently tracer
> supports other package managers as well as dnf. It also seems to be
> trying to offer more interactivity about what to restart and why, but I
> don't generally bother with that.
>
To reiterate. The only reason I don't use the tracer plugin is that it runs
*automatically* and, depending on the number and type of updates can interfere with
the also automatic process of updating the nVidia kmod packages. Certainly the same
problem could happen if you manually run needs-restarting right after an upgrade that
includes a kernel upgrade. But, presumably, you'd know better. :-)
Sure.
poc