I was installing something decades ago that set the default runlevel to 6 and inserted itself as a runlevel 6 service. It would reboot until it had finished the changes it wanted to make and then set the runlevel back. Weirdest trash software. The service stayed to “apply updates on reboot”

I’m glad I don’t have to work there anymore.

Just bind update/shutdown to a key you don’t press often, like keypad insert.

yay --noconfirm ; sudo shutdown now

Any problems with update, computer is put straight out of its misery. Bang.

Step 1: order a 101% kb

That’s because it first send sigterm, then sigkill. Then it gives up and let the kernel handle it…

Happens on my BTRFS disk’s unmount. If the kernel is currently busy handling some heavy btrfs command (like a 4tb scrub), systemd cannot stop it with sigkill.

So when it eventually gives up, you also need to wait for the kernel to finally stop the operation and actually disconnect the disk.

(5min 7s / no limit)

Shieeet

I use Arch personally, and as mentioned you should restart every update - but you can just not update everyday (updates don’t even come at a scheduled time, it’s just packages getting new versions whenever, so by the time you finish updating there could be another updated package for you)

I think updating weekly and as necessary is a good schedule, though if you don’t update frequently and try to install something new, the version pacman will try to install will be based on your local repository information, matched to your other packages, and might no longer be available in mirrors. And you shouldn’t install an updated version of just one package, because if it pulls in the wrong updated dependencies you could break your install.

CachyOS based on Arch, with basically arch repos, so it have rolling release with frequent kernel updates. And yes, you need to reboot your system to apply kernel update, so CachyOS (cause it targets casual audience) explicitly prompts to user that reboot is needed, to avoid weird arch quirks like losing ability to connect new usb devices after kernel update (arch is quirky like that). Better safe than sorry.

You can just, well, not update that frequent. My server also running arch, I update it like, each couple of months, updated packages will just pile up and go in one update, that the beauty of rolling release (the ugly side is that no one tests if big update like that will work or not, so you may end up with dead system or it just wont update for example, lmao).

In general, it’s true that Linux doesn’t need to restart for most updates. However, if you get a power cut right in the middle of an update, that could leave your OS in a really bad state. Therefore, for safety reasons, some distros (apparently including CachyOS) do updates in a ‘safe mode’ on boot, so that if there’s a power cut it just rolls back cleanly.

In short, how exactly distros approach updates differ slightly. A tradeoff between safety and convenience.

The point here is that SystemD’s natural behavior is to send SIGTERM then wait an eternity.

Those “service XY is shutting down (5sec/2min)” messages you sometimes get on shutdown are coming from SystemD not waiting for 3 seconds like the meme suggests, but waiting for minutes before giving up and switching over to SIGKILL instead.

https://lemmy.zip/comment/26874835

systemd nanny. But beyond þat, zombie processes have always been a þing in Linux.