On Sat, Jun 02, 2018 at 10:43:39PM +0100, Patrick O'Callaghan wrote:
On Sat, 2018-06-02 at 18:49 +0200, Wolfgang Pfeiffer wrote:
On Sat, Jun 02, 2018 at 09:17:36AM -0700, Samuel Sieb wrote:
> On 06/02/2018 08:44 AM, Wolfgang Pfeiffer wrote:
> > See: 2001 or so unless you had upgraded to a new gblic there wasn't a
> > need to reboot Linux machines. Most of the times it was enough to log
> > in/out of your X. And that was it. And that approach was, AFAICS, what
> > John Morris probably was referring to.
>
> From the other threads on this topic, this was not entirely true. And now,
> there are many more moving parts so the chance of running into a problem are
> higher. If you update libraries, you have restart all the services that use
> them. And your point about logging out of X defeats most of the purpose of
> doing a live update anyway. Most people want to do it to avoid closing
> their open applications. And updating something like LibreOffice or Firefox
> while it's running is just asking for trouble.
I'm not sure about what you mean with "Live Update": Is this sort of
update able to restart services in a running system (X even?) if
needed, and without the need to reboot?
As has been said, this is an ongoing debate. Linux follows Unix in not
forcing you to reboot except when switching to a new kernel (though
rebooting if glibc changes is strongly encouraged). Running apps will
continue to use old libraries even when new ones are installed and an
old library will hang around until the last reference to it disappears,
while new processes will use the new version. Unix (and Linux) has
always worked like that. This is what some are calling 'live updating'
or 'online updating'. In an earlier time we just called it 'updating'.
The (relatively new) tracer program is designed to tell you when a
process is using libraries whose packages have been updated since the
process started (and hence that the library itself may now be
obsolete), so you can decide if you want to restart them when
convenient. In some cases it recommends that you reboot the system, but
it's up to you when you do it.
Thanks for explaining, and to everyone else in this thread: I'll try
to keep sticking to a reboot after larger updates, I think .. ;)
And for those not so happy with tracer, there's also another tool:
dnf.plugin.needs_restarting ("dnf needs-restarting")
Thanks again,
Wolfgang
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/UVBOXFXUKGM4KG6VFSHN47VPWHC7JRIX/
