On 9/14/2013 9:53 AM, Dylan wrote:
On 14/09/13 17:23, Anton Aylward wrote:
Felix Miata said the following on 09/14/2013 11:01 AM:
On 2013-09-14 10:15 (GMT-0400) Anton Aylward composed:
Restarting the kernel needs a reboot just as installing a new kernel as part of installing a new distribution needs a reboot. No way around that.
ROTFLMAO!
<quote> This avoids the long times associated with a full reboot </quote>
*WHAT* long times?
Indeed - and from the docs it seems kesec goes through the software shutdown/restart procedures and only omits the hardware/bios reset. For me, reboot takes 50seconds to KDE log on screen *including* the grub timeout, so skipping the hardware reset would save save at most 10 seconds. Even if I'm really in a hurry, what's the difference? Especially since all services need to be stopped anyway...
Dylan
That is fine for YOU. But with a multi-user machine, or won that is serving some other clients as a file-server or database server, you frequently need to roll the machine to replace modules that are continuously in use by multiple users. This isn't a new problem, its been around for as long as I've been using linux. Old versions of some critical software don't always mix well with new versions. The old executable will usually run just fine, but if it makes occasional use of some configuration file, it may try to open the new version, sometimes with bad results. Virtually anything having to do with Gnome or KDE you can simply log out, and log back in again. But for services provided across the network, this doesn't work. If you can't be down, then don't update. Its that simple. Or at least don't update until a scheduled maintenance window. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org