On Sat, 2018-06-02 at 20:03 +0800, Ed Greshko wrote:
On 06/02/18 17:09, Patrick O'Callaghan wrote:
> On Fri, 2018-06-01 at 21:45 -0700, Samuel Sieb wrote:
> > On 06/01/2018 09:32 PM, John Morris wrote:
> > > On Fri, 2018-06-01 at 11:30 -0700, Samuel Sieb wrote:
> > >
> > > > You did online updates? This is the reason why offline updates is
the
> > > > default now, because doing updates without a reboot can cause weird
> > > > situations like this.
> > >
> > > Ok, you maniacs finally did it, you made a Linux suck as hard as
> > > Windows. I'm out.
> >
> > Seriously? This discussion comes up regularly. In most cases online
> > updates work, but sometimes there are issues. Read the past threads for
> > more info, but it's an extremely hard problem to make it always work for
> > very obvious reasons when you think about what's happening.
>
> I rely on tracer (using the dnf plugin) to tell me when I need to
> reboot. Are you saying this is unreliable?
>
Where did Sam say anything about tracer?
He didn't. I merely state that it it's useful to know when a reboot is
necessary and when it isn't, which is the difference between online and
offline updates.
FWIW, I don't use the tracer dnf plugin since I use the nVidia
drivers from rpmfusion
and akmods. It may have been improved. But when I was using it and a kernel update
happened the tracer process would keep the rpmdb locked so when the nVidia mods were
compiled they failed to install.
I haven't had problems but I don't use the Nvidia drivers now. Back
when I did use them I also had locking issues, though I never
associated them with tracer specifically.
poc