I don’t know runit. Maybe runit didn’t even have a way to delay or customize shutdown, maybe it always just waits 5 seconds and then forcibly terminates a process, resulting in you never noticing when a cleanup job was too slow. Maybe you just randomly never installed a particular program with a slow shutdown job while using runit. There’s a bunch of reasonable explanations and possibilities for why this difference exists, and they can all mean systemd is perfectly reasonable.
I don’t know runit. Maybe runit didn’t even have a way to delay or customize shutdown, maybe it always just waits 5 seconds and then forcibly terminates a process, resulting in you never noticing when a cleanup job was too slow. Maybe you just randomly never installed a particular program with a slow shutdown job while using runit. There’s a bunch of reasonable explanations and possibilities for why this difference exists, and they can all mean systemd is perfectly reasonable.
Alright man, fact remains i was just making a silly joke, you don’t have to be poettering’s pr team lol
You’re the one who brought up runit and insinuated it doesn’t have this problem ¯_(ツ)_/¯
I said i never experienced this problem with runit, not that it can’t happen. It was anecdotal.