Colin Walters (walters@xxxxxxxxxx) said:Actually, libvirtd does restart on upgrade. It's implemented in the
> 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.
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 isReally? I think we're moving more towards a model on mobile devices where
> 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.
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.
-- Fedora-desktop-list mailing list Fedora-desktop-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-desktop-list
