FF v dnf needs-restarting

[Bojan Smojver]

I'm guessing most of you here probably observed this behaviour with dnf when FF is upgraded. Even after FF restarted, dnf needs-restarting reports that it needs restarting. Does that sound like a bug or is this somehow intentional?

I'm seeing this in f29 and previous releases are the same. Once I upgrade to f30, I'm planning to open a bug on this if it's still the same, unless someone tells me this is how it's supposed to work.

Thanks,

[Kamil Paral]

On Tue, Apr 16, 2019 at 4:56 PM Bojan Smojver  wrote:
> I'm guessing most of you here probably observed this behaviour with dnf
> when FF is upgraded. Even after FF restarted, dnf needs-restarting reports
> that it needs restarting. Does that sound like a bug or is this somehow
> intentional?
>
> I'm seeing this in f29 and previous releases are the same. Once I upgrade
> to f30, I'm planning to open a bug on this if it's still the same, unless
> someone tells me this is how it's supposed to work.

I see the same behavior (F29). However, "sudo tracer -ea" doesn't complain
about Firefox. The question is which tool is correct. My current guess is
tracer.

[Miroslav Suchý]

Dne 17. 04. 19 v 9:54 Kamil Paral napsal(a):
> The question is which tool is correct. My current guess is tracer.

+1
needs-restarting is very simple plugin. Tracer [1] is more sophisticated and I encourage everyone to use Tracer instead
of needs-restarting.

Miroslav

[1] https://apps.fedoraproject.org/packages/tracer

[Dominik 'Rathann' Mierzejewski]

On Tuesday, 23 April 2019 at 09:29, Miroslav Suchý wrote:
> Dne 17. 04. 19 v 9:54 Kamil Paral napsal(a):
> > The question is which tool is correct. My current guess is tracer.
>
> +1
> needs-restarting is very simple plugin. Tracer [1] is more
> sophisticated and I encourage everyone to use Tracer instead of
> needs-restarting.

Last time I used tracer, it had several issues. It was breaking
dist-upgrades and hogged the CPU for tens of seconds after the dnf
transaction was done. needs-restarting can be run after multiple
dnf updates.

Is it better nowadays?

Regards,
Dominik

[Kamil Paral]

On Wed, Apr 24, 2019 at 9:20 AM Dominik 'Rathann' Mierzejewski <
[e-mail]> wrote:
> Last time I used tracer, it had several issues. It was breaking
> dist-upgrades and hogged the CPU for tens of seconds after the dnf
> transaction was done. needs-restarting can be run after multiple
> dnf updates.
>
> Is it better nowadays?

Tracer seems pretty fast now. It also seems pretty reliable (compared to
needs-restarting, which sometimes shows bogus processes, and sometimes
doesn't show processes which tracer identified correctly).