follow-up: update, reboot required?

[Lee]

On 3/19/22, Lee <ler...@gmail.com> wrote:
> On 3/19/22, piorunz wrote:
>> On 19/03/2022 02:32, Lee wrote:
>>> How to tell if I need to reboot the machine after updating the software?
>>
>> install "needrestart" package.
>>
>> Description: needrestart checks which daemons need to be restarted after
>> library upgrades.
>> It is inspired by checkrestart from the debian-goodies package.
>
> Yes! Thank you!!
>
> It seems to me that "checks which daemons need to be restarted
> (needrestart)" won't catch as much as "check which processes need to
> be restarted (checkrestart)" so I'll try both but I'm probably going
> with checkrestart

I'm keeping both needrestart and checkrestart.

Synaptics Package Manager calls needrestart at the end to a) show what
things need to be restarted and b) allow you to easily restart them,
so that stays.

My problem with needrestart is that it doesn't show everything that
needs to be restarted.
Maybe it's the difference between 'daemon' and 'process', but
checkrestart gives a better list of what all needs to be restarted.
For example:

$ sudo needrestart -r l
[sudo] password for lee:
Scanning processes...
Scanning candidates...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

Services to be restarted:
systemctl restart named.service

Service restarts being deferred:
systemctl restart NetworkManager.service
/etc/needrestart/restart.d/dbus.service
systemctl restart lightdm.service
systemctl restart systemd-logind.service
systemctl restart us...@1000.service
systemctl restart wpa_supplicant.service

No containers need to be restarted.

No user sessions are running outdated binaries.


$ sudo checkrestart
[sudo] password for lee:
Found 36 processes using old versions of upgraded files
(25 distinct programs)
(20 distinct packages)

Of these, 3 seem to contain systemd service definitions or init
scripts which can be used to restart them.
The following packages seem to have definitions that could be used
to restart their services:
network-manager:
555 /usr/sbin/NetworkManager
bind9:
717 /usr/sbin/named
pulseaudio:
2323 /usr/bin/pulseaudio

These are the systemd services:
systemctl restart NetworkManager.service
systemctl restart NetworkManager-dispatcher.service
systemctl restart NetworkManager-wait-online.service

These are the initd scripts:
service named restart
service pulseaudio-enable-autospawn restart

These processes (17) do not seem to have an associated init script to
restart them:
xserver-xorg-core:
766 /usr/lib/xorg/Xorg
pipewire-bin:
2322 /usr/bin/pipewire
2327 /usr/bin/pipewire-media-session
xfce4-session:
2333 /usr/bin/xfce4-session
at-spi2-core:
2400 /usr/libexec/at-spi2-registryd
xfwm4:
2413 /usr/bin/xfwm4
xfce4-settings:
2426 /usr/bin/xfsettingsd
xfce4-panel:
2450 /usr/bin/xfce4-panel
thunar:
2454 /usr/bin/thunar
xfdesktop4:
2459 /usr/bin/xfdesktop
xfce4-power-manager:
2462 /usr/bin/xfce4-power-manager
xfce4-notifyd:
2470 /usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-notifyd
policykit-1-gnome:
2478 /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
system-config-printer:
2480 /usr/share/system-config-printer/applet.py
network-manager-gnome:
2487 /usr/bin/nm-applet
light-locker:
2494 /usr/bin/light-locker
libxfce4panel-2.0-4:
2512 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
2516 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
2517 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
2518 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
2519 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
2521 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
2523 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
2524 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
gvfs-daemons:
2550 /usr/libexec/gvfs-udisks2-volume-monitor

Maybe it's just my ignorance, but checkrestart does a better job of
telling me 'you need to reboot.'

Thanks everyone for all the feedback earlier.

Regards,
Lee

[Kushal Kumaran]

On Sat, Apr 23 2022 at 01:11:49 PM, Lee <ler...@gmail.com> wrote:
> On 3/19/22, Lee <ler...@gmail.com> wrote:
>> On 3/19/22, piorunz wrote:
>>> On 19/03/2022 02:32, Lee wrote:
>>>> How to tell if I need to reboot the machine after updating the software?
>>>
>>> install "needrestart" package.
>>>
>>> Description: needrestart checks which daemons need to be restarted after
>>> library upgrades.
>>> It is inspired by checkrestart from the debian-goodies package.
>>
>> Yes! Thank you!!
>>
>> It seems to me that "checks which daemons need to be restarted
>> (needrestart)" won't catch as much as "check which processes need to
>> be restarted (checkrestart)" so I'll try both but I'm probably going
>> with checkrestart
>
> I'm keeping both needrestart and checkrestart.
>
> Synaptics Package Manager calls needrestart at the end to a) show what
> things need to be restarted and b) allow you to easily restart them,
> so that stays.
>
> My problem with needrestart is that it doesn't show everything that
> needs to be restarted.
> Maybe it's the difference between 'daemon' and 'process', but
> checkrestart gives a better list of what all needs to be restarted.

All the extra stuff reported by checkrestart below is part of the user
session. needrestart has reported it as "us...@1000.service". It means
that user needs to log out and log back in.

When needrestart reports any restarts being deferred, that indicates
services that have been specifically marked as being disruptive if
casually restarted. Proper way to deal with those would involve either
logging out and back in, or rebooting. Anything involving display
manager, login management, or dbus is safest dealt with by rebooting.

For my own situation (single user laptop), I simply reboot whenever
needrestart defers anything and don't bother with logging out.

> <snipped output from {check,need}restart>

--
regards,
kushal