On Tue, Sep 29, 2009 at 6:51 PM, Bill Nottingham notting@redhat.com wrote:
Colin Walters (walters@verbum.org) said:
For system-level services, we have the idea of try-restart on upgrades;
if
the service is running, we automatically restart it on upgrade.
How does that work? Obviously you can't restart packagekitd while it's
in
the middle of upgrading. Another one you obviously can't just kill and restart is libvirtd.
Actually, libvirtd does restart on upgrade. It's implemented in the init scripts.
But...hm, ok, so all of the state is in the config data/cache, and child qemu processes I guess. The real point here is the qemu processes.
The live replace files on disk part of upgrade is also problematic, and is
actually the most broken thing relating to updates we have right now.
For
this reason among others I think we should move to installing updates immediately before logout/reboot.
Really? I think we're moving more towards a model on mobile devices where there *is* no logout/reboot except by accident in a large number of cases.
The update system should prompt to start installing updates and automatically do a logout/reboot as necessary.