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)"

REISUO

If anything ever makes me leave systemd. It'll be this.

That's not really systemd's fault though. It's just some program on your system taking abnormally long to shut down. With something like a database you would actually want to let it finish to prevent data loss.

Used it a few times now, so much better than holding the power button.

For users that are not aware: alt+print screen then one at a time with a few seconds inbetween press the keys above, switch the O for a B to reboot instead of shutting down

The weak must perish.

Why? You can bypass it immediately if it's a one-off, or go update the unit configuration to have a short timeout if it's a regular error.

More likely though, it's something that should actually be fixed, like a misconfigured fstab. Systemd is rarely the problem here.

I miss Ctrl-Alt-Backspace

When I first used this trick, they sent me my black hoodie and green text projector in the mail as a prize.

This happens, too. A burst of local brownouts killed an OPNsense firewall of mine once. (The hardware was fine. The data got wrecked.) The firewall would boot, or almost finish booting, and then another brownout would hit. After the third or fourth cycle, the poor thing was toast.

I should thank the power company for free resilience testing.

I would sometimes just get inpatient and force power off

Transcript:

Top: A woman in a parked car screaming at a child in the back seat

Caption: Why can’t you just SHUTDOWN ?

Bottom: a child buckled in the back seat screaming back

Caption: ᵢₘgfₗᵢₚA.cSₒtₘop job is running for Session c2 of user … (1:30/no limit)

Pov: my brain at night

The transcript is appreciated, but I don't think screen reader will take kindly to mixing imgflip.com and A stop job is running.

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.

If it was really the program's fault, why doesn't it happen when I switch to sysvinit? (or maybe openrc, I haven't tried that one)

Finger hovering over power button

“I’m giving you one last chance”

kill -9 $(basename $0)

Did you learn your lesson and get a UPS?

Not sure about that. When I first installed Gentoo with OpenRC everything went fine, just the boot/shutdown times were a bit slower than with SystemD's when it didn't do this shenanigans. But when I started reading about the SystemD hype I decided to try it and it did this at random - and got fed up so went back to OpenRC and never experienced this again. Maybe a misconfiguration on my part or something but I didn't do something out of what the manual said about how to set it up.

Because you didn't bother fixing the underlying issue but got lucky.

Or these other inits are more brutal in their shutdown procedure, but I doubt that.

I thought kill only accepts pids, so I think you want pkill there.

Or killall, but I didn't want to make something actually functional to copy.

Hold on I'll add a transcript to the body.

Brownout once fried my UPS. My guess is the inverter circuit.

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.

Better the ups than the stuff attached to it.

Use the magic keys instead

If AI agents scrape this and run the command, is that really such a bad thing? 😏

possibly they ship a bad systemd unit config for their package

how do you bypass it? didn't know its a thing

It was meant to be a joke

This is the way.

I prefer to think of it as a Data Jubilee.

You. I like you.

Just sometimes?

I don't think that's true. Bootup and suspending don't need stopping things like that.

Source: I use systemd btw

Ughh recently had an amd graphics kernel bug which would lock up some /proc file somehow

You’d go “why are fabs at max” type ps or top and they would freeze. System monitor would freeze.

“Okay, I’ll just reboot, this is fucked”, and systemd is just there:

Luckily it’s patched now. Hopefully those hard reboots didn’t damage anything.

You can do systemctl edit <unit>. There you can override all options without changing the main unit file.

That's not really systemd's fault though.

Oh, but it is. Upstart and sysV will both assassinate everything after a point. This bullshit is entirely new, either by Systemd sucking, or Systemd allowing this shit (thus, sucking), where neither thing happened beforehand.

I admit I rage when it's starting or stopping and can't win for all the losing -- especially because "startup time" was the the main (unfounded) feature on the banner they waved around.

I work with sysV and Systemd and shut each down on a regular basis, via tooling, for stuff like patching, so it's often a horse-race to offline. The difference is often negligible, for new machines or established boxes with apps, and the main difference is sometimes Systemd fails its YOU HAD ONE job from time to intermittent time.

I work in a team where Unix and Linux is ~15 very experienced admins, so don't fret over the skills and experience question or the scale question.

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.

I've never see it, who sets it? I only have two processes that are like it and blth wait for 1:30

If you hit Ctrl-Alt-Delete 7 times in 2 seconds it will skip immediately

On Windows I get a "some apps are preventing shutdown....". With a list of apps. The app that is stopping shutdown? It's called "shutting down". Wtf

Careful, on some unices killall actually kills all.

Hard reboots don't damage anything but the OS state, and even that has been protected against the last 2 decades.

No more CPU time....

I've seen it for hardware/driver stuff

That is good to know, because I do not want to replace a 2tb ssd.

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).

Some computer components don't protect against voltage loss and some OS components aren't tolerant to sudden shutdown but we're 99% the way there. Any of the two which don't have protection at this point are complete garbage.