1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-09-19 20:02:10 +00:00
seirdy.one/content/notes/kexec-considered-overkill.md
2022-10-23 22:09:27 -07:00

1 KiB

title date replyURI replyTitle replyType replyAuthor replyAuthorURI
Kexec considered overkill 2022-10-23T22:09:27-07:00 https://community.mojeek.com/t/kexec-boot-a-new-kernel-without-power-cycling/ Kexec: Boot a new Kernel without Power Cycling DiscussionForumPosting Mike https://community.mojeek.com/u/mike/

Avoid kexec if you don't need it: it opens new vulnerabilities, and is better left disabled for most use-cases. Redundancy and failover should eliminate the need when hosting a typical service. Even without the risks, there are other reasons to reboot: updates to shared libraries, SELinux policies, and init systems often warrant one.

One use-case that benefits from kexec is pubnix systems with many logged-in users. If you need to apply an unscheduled security patch while causing minimal disruption, then live-patching makes sense.

With some boot optimization, I can hit 99.9% uptime even if I reboot 2-3 times per week on Fedora. With failover, these reboots should have negligible impact.