On 09/07/2017 05:20 PM, Andrew Toskin wrote: >> Den 2017-09-07 kl. 14:16, skrev Wolfgang Pfeiffer: >> You only need to reboot if the kernel is updated. > > Supposedly there are ways to get around this even this, but I can't find a way to make it work. > > kSplice smoothly switches the running system to the new kernel, but Oracle acquired the project and made it proprietary, so the only way to use it is with an enterprise subscription. > > Red Hat then announced a free/gratis and open source alternative called kpatch. You could try it, but as of today, it's still not considered stable enough for production use -- https://github.com/dynup/kpatch > > Then apparently Red Hat and openSUSE merged parts of both of their competing implementations into the kernel itself? -- http://www.zdnet.com/article/no-reboot-patching-comes-to-linux-4-0/ -- But I can't find anything about how to *use* this feature. I'd be very suspicious of trying to use a new kernel without actually _booting_ the new kernel. There were abortive attempts to partially restart the kernel with the Mach kernel. It sorta worked...in fairly rare occurrences...but never reliably and often ended with the system crashing in fairly ugly ways. Both Apple, Carnegie-Melon and DEC gave it the old college try. My basic rules of thumb is...if the kernel was updated, reboot. If glibc was updated, you could restart your apps but it's safest to reboot. I mean, do you do an engine swap on your car when you're tooling along at 80MPH? I sure don't! ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - If this is the first day of the rest of my life... - - I'm in BIG trouble! - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
