Transcript:
Two panel meme.
Top panel: Woman in the front seat of a car screaming at a child in the rear seat. She’s saying “Why can’t you just shutdown?”
Bottom panel: A child screaming “A stop job is running for Session c2 of user … (1:30 / no limit)”
That can hit any time, not just in shutdown. At bootup, when suspending, etc. This message and the wait time is so bad. Systemd basically implemented Windows Update waitouts on Linux! It’s incredible!
Switching from systemd to sysvinit solved that pretty nicely.
I don’t think that’s true. Bootup and suspending don’t need stopping things like that.
Source: I use systemd btw
Oh but it’s not just stopping things, starting things is subject to the same issue also:
A start job is running for "wait for network to be available"(attached to a network interface that is not necessarily connected at bootup)
Systemd is just special.
https://askubuntu.com/questions/972215/a-start-job-is-running-for-wait-for-network-to-be-configured-ubuntu-server-17-1
Well I guess that tells you everything.
You didn’t solve the problem. You only ignored it. Systemd does exactly what it’s instructed to do. If a program takes longer it waits if it’s instructed to do so. It’s well defined and predictable. Much better than a random assortment of bash scripts. And it’s incredibly customizable. If the defaults don’t fit you, you can easily override them without touching the main unit itself.
Oh no, I solved the problem: I uninstalled systemd. It’s systemd who is ignoring things, such as the longstanding history of Unix and Linux (research what happened between systemd and screen, tmux, dtach).