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)”
Idk if this is a hot take but „no limit“ should straight up not exist. Just set a limit and blow the whole PC up when it takes too long.
Due to what I call some quirks (but what other people call “good, sane, excellent design decisions”), you can set a hard timeout… that can be flatly ignored by systemd for various reasons that might or might not be obvious. In that case it will happily show you
<current timer> / <timeout>, then move to<current timer> / <timeout * 2>, and so on.Because that, for some reasons, makes a lot of sense to some people that are not me.
Lots of things make no sense to some people that are me.
Lennart Poettering deserves all the hate he gets and then some…
Just set the limit to something sane like 2³² seconds!
Now you’re thinking with squares!
I’m ngl if I see this shit, I just hard power-cycle the machine. I ain’t got time for that.
I’ve never see it, who sets it? I only have two processes that are like it and blth wait for 1:30
The only time I see it is to do with mounting my NAS at boot and unmounting it on a shutdown.
I’ve seen it for hardware/driver stuff
Yup, as happened during my most recent linux suicide, dracut just waits infinitely for a device to mount (tho it drops into a emerg shell after like 3 mins or so).
This is the way.