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 "user@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
