Hello, Am Dienstag, 19. Februar 2013 schrieb Ruediger Meier:
On Tuesday 19 February 2013, Philipp Wagner wrote:
Am 19.02.2013 12:36, schrieb Michal Kubecek:
You are talking about protecting the user from a potential application crash after an update. But you forget to tell us that
It's usually not a crash, Firefox is just malfunctioning. So
Don't forget that there are a lot systems where users never log off or where other important processes have to run 24/7. These systems are IMO the more important ones.
Agreed, rebooting is not the solution (except for kernel updates ;-)
BTW firefox is really a bad example to satisfy offline updates because usually it is malfunctioning very often in cause of many other reasons. So no user would wonder about it. Or "help" your users by doing ... $ killall -11 firefox ... still less annoying than asking them for reboot.
*lol* Some mails up, I read that ubuntu ships a firefox extension that asks the user to restart firefox after an update. Couldn't we just "steal" this extension? ;-) If I may add another wish/idea - it would be nice if I could just do something like zypper ps | systemctl restart --stdin or, alternative implementation, zypper ps --restart ;-) Oh, BTW: I'm even zypper dup'ing to the latest Factory while working in KDE. I don't say it always works without problems (but the problems I remember were a) small and b) rare), and it causes significantly less annoyance that waiting for a Factory update on shutdown. Regards, Christian Boltz -- Also nochmals bitte Entschuldigung an alle procmail-Fans! Ich denke man muß sich für ein Tool entscheiden, und muß halt dann alle Features und Bugs in Kauf nehmen; also so ähnlich wie bei Frauen ... ;-) [Ralph Müller in suse-linux] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org