On 11/07/18 09:06, Richard Kettlewell wrote:
> The Natural Philosopher  writes:
>> On 10/07/18 16:40, Grant Taylor wrote:
>>> On 07/10/2018 06:02 AM, Alister wrote:
>>>> for all other upgrades a reboot should not be required
>>>
>>> I think it is STRONGLY recommended to reboot when replacing other
>>> core files like the C library that just about everything else on the
>>> system uses.
>>>
>>> I think there are ways around this, but they are cumbersome and error
>>> prone.  Their failure will end up in a crash followed by a reboot.
>>> So it's just best to plan for the reboot when doing the update that
>>> modifies the kernel and / or core OS libraries.
>
> In Debian (and therefore presumably also Raspbian) a libc upgrade will
> automatically result in a lot of services being restarted.
>
>> AIUI any program that uses the core libs will run on, on the old libs
>> until its repoened,. so there is no need to shutdown the mnachine,
>> just the apps using the libs, and then there is no hurry.
>>
>> The only app Ive ever seen go unstable after an upgrade unless
>> restarted is firefox.
>
> NSS functionality is the main issue; presumably the ABI is tightly
> couple to the specific libc version.
>
No, this isn't after a libc update, it's after a FIREFOX update.

I can only assume that firefox revisits itself on the hard disk in
someway and loads in bits that no longer match whats running.



--
Microsoft : the best reason to go to Linux that ever existed.

--- SoupGate-Win32 v1.05