On Tue, Feb 19, 2013 at 02:01:35PM +0100, Philipp Wagner wrote:
It's usually not a crash, Firefox is just malfunctioning. So actually offline updates would prevent the users from having a malfunctioning (partly working) application.
By shutting it down completely. And by shutting it down even in the case when Firefox isn't actually updated at all.
If instead the updates are applied on a reboot during regular maintenance intervals (e.g. at 3am when nobody is logged in), all users are better off.
I guess we should start with making clear what users we are actually talking about. I guess users running Firefox via "ssh -X" or from a traditional X terminal are not the use case we should tailor our solution to. The user logging into KDE/Gnome and running an update from there is not a problem - he knows to run "zypper ps" (and zypper actually tells him to do so when it is needed) and can decide what to do according to the result. So when we are talking about users and their running application, my understanding always was that we are talking about the case when a desktop is shared by a bunch of users who log into a desktop environment of their choice and rather then logging out, they just lock the session so that another user can come and switch to his session or start a new one. And I really don't see any advantage of offline updates in this case. With this setup, to be able to reboot without shutting down all sessions (except mine), I would have to ask all users to log out first. Which is not easy to achieve and I would certainly prefer to avoid it when possible and reboot such system only when I really need to. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org