A stop job is runningAt least it tells you how long it’ll take before it decides to SIGKILL whatever is holding the shutdown sequence.
Well you say that, but I’ve seen the countdown go past and then reset to a higher number often.
I entrust you with this horror, go figure out what to blame.
shutdown-analyze.sh
#! /usr/bin/env bash shutdown_start=$(journalctl -b -1 -u systemd-logind --grep="System is (powering down|rebooting)" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP) shutdown_start=$((shutdown_start / 1000000)) units=$(journalctl -b -1 --since=@$shutdown_start --output=cat --no-pager --output-fields=UNIT JOB_TYPE=stop CODE_FUNC=job_emit_start_message) for u in $units; do stopping_start=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_start_message _SYSTEMD_UNIT=init.scope) stopping_end=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_done_message _SYSTEMD_UNIT=init.scope) duration_human=$(systemd-analyze timespan $((stopping_end - stopping_start))us | tail -1 | sed 's/.*: //') printf "%s\t%10s %s\n" $((stopping_end - stopping_start)) "$duration_human" "$u" done | sort -rn | cut -f 2Thanks, I usually know what it is tho. Most often it’s VMs I was using for testing stuff, which I forgot to shutdown. It takes a while for them to cleanly shutdown, which is what the wait is for. I have a shortcut on my desktop to a script that checks for any running VMs still and shuts them down. But I forget to click it sometimes and then I have to wait. No big deal, except I like to switch off the power bar that powers the computer and everything attached to it. An old habit from when such a thing mattered, these days standby power is probably nothing to worry about. But still I wait patiently for the computer to shut down till I switch off the power strip.
If your script somehow shuts them down faster than plain old SIGTERM, putting it under
/usr/lib/systemd/system-shutdown/might be a good idea. Checkman 8 systemd-shutdownfor more info on that.
I think that depends on the setting, I had situations where one of my docker containers took ages to shutdown and it would just say 00/02 00s but when it reached that limit, it would just go up.
Individual services can override the default 90 seconds timeout. But then you can override their override if you think you are smarter, of course.
Alt-SysRq-i, u, oI don’t have time for this shit.
have i learned a new magic combo?!
(X time / 1:30) but the second time will be extended indefinitely for some fucking reason.
Why can’t it say what the job is 🧐🧐🧐
Actually, it usually does. I was just too lazy to think of one.
Yes but no, u can in config file of systemd change timeout to 5,10 second or other number of seconds which u wish before it will kill it
[** ] A stop job is running for Session c1 of User gdm (49s / 1min 30s)`[** ] A stop job is running for Session c1 of User gdm (4min 19s / 1min 30s)`
You read my mind
Reminds me of one of the truest comics I ever read.
It is weird isn’t it.
Why do they make it so bad?
I imagine half of linux users could make better automated update rules in their cron.
So many better ways.
So why are they making it intentionally bad?
… Sabotage from Microsoft employees who hate Microsoft?
… Part of a larger Embrace Extent Extinguish tactic, where they’ve already embraced the Linux Foundation etc enough, they’re ready to extinguish Windows, already having sufficient monopolistic total-control hooks in Linux???
What are they up to? There has to be a reason it’s so bad. There has to be a reason they go out of their way to make it so bad.
It surely can’t just be the effects of The Corporation, the hierarchies and compartmentalisations and bureaucracy of the structure where they don’t understand (or even perhaps do understand [and maybe have seen Kevlin Henney’s excellent talk on clean code vs enterprise programming] but) can’t do anything about it, can it?
What are they building in there? We don’t get to see, we don’t get to know, just trust them, they know best when and how, and so you are not allowed to change it.
We are not doing that any more.
Having a monopoly makes you arrogant. That is probably the only reason why they do it.
Maybe train you into avoiding shutdowns, never shutdown, stay on Microsoft windows for ever, forget about other things like sleep or eating.
Windows has had always a problem: unlike Unix, where files are referenced by an inode where the name points to, Windows has the names directly linked to the files. When Windows needs to update a system file that is in use it has to stop being used. And for some system files there only one way to do it: reboot. On Unix, the name of the file can change the inode where it points to and the system goes on. The old file exists until every proves stops using it and then is erased while new processes access the new file. So no reboot is needed.
That leads to not having to update everything on reboot. Only the kernel and little more.
Windows cannot shut down because there is a folder open.
Windows cannot shut down because Bill still wants to keep watching you to see what you’re doing.
Windows cannot shutdown because there’s a Windows open.
You can just type “shutdown now” and it does.
Or just
poweroff, one word not twoHow about
halt
*Holds power button on windows device
Isn’t it crazy that you need a physical workaround for your operating system?
To to honest my Fedora install used to hang indefinitely 20% of the time I tried to shut it down. So I also became well acquainted with that solution
It is a last ditch effort in Linux instead of the first reaction for me in Windows.
Maybe I don’t just don’t respect Windows. It probably goes back to things like it deciding to do an unskippable update right before I did a presentation or trying to find some obscure .dll file for hours trying to make a program work.
I get your point though.
Fair enough considering Windows also doesn’t respect you. My worst experiences were the times I accidentally clicked on “update and restart” so I just had to wait there after a long night of getting a presentation or homework done. That happened a few too many times in high school.
But I barely handle updates myself these days. I have set it to automatically* apply them live for my year on Silverblue. I have something similar for my phone updating every weekend at night considering I sleep in anyway. This post did remind me how nice it is to not have to worry (or even think) about updates.
*I do manually update between major Fedora releases. But those happen twice per year so yeah.
Sure I guess. There’s plenty of things better about Linux so why lie? This meme misses the mark is all I’m saying.
I was just pointing out the irony of your statement. I think this is a low effort meme for sure
Who needs their files closed and disks synced, anyway?
Are you guys really using a command to shut down a computer?
Because you can do the same with Windows, but nobody uses it because it is just not convenient to use commands for that.
shutdown /s“please shut down (this is sarcasm)”
Yeah, you can even throw a /f in there to force close all apps so it will kill everything and go nighty night. I used to use it with /t command if I wanted to download something while I was out but not have the PC run all day.
That’s not the best way to turn your PC off but hell half the time I just murder mine by holding down the power button anyways. As long as you’re not being crazy shutting her down in the middle of some data operations you’ll be fine.
I used it when I was watching movies to fall asleep to but did not want to use the battery. You can specify a time with /t before the shutdown occurs.
I always did a
sleep 1h && systemctl suspend
Reminds of a couple [(brilliantly delivered, poignant)] lines from the movie Sphere.
“I hope it doesn’t have any feelings.”
“What happens when he gets upset?”
[Thanks LLM on a websearch for helping remember it was from the Sphere, not 2001, lol… different similar(ish) lines in that. ~ Wait, why am I thanking the LLM? … Does this speak to how gratitude’s good… Or in expressing this gratitude, does it suggest I suspect, on some level, perhaps subconsciously, that the LLM has feelings!?!! Oh well at least we’re not putting LLMs into our local computers that we shutdown. …]
I was always particularly fond of windows turning my laptop on, running updates, and then going into hibernation, which then caused a blue screen trying to come out of it.
The laptop had sleep and hibernation disabled, all of the wake-on-events and automatic updates were disabled as well. (It was an older cranky thing and deserved rest - or to be taken out back and shot.)
Yet, somehow it always turned on for update day, even after I blocked it from the internet via the router.
(It was an older cranky thing and deserved rest - or to be taken out back and shot.)
Or gifted something like GNU+Linux, BSD, OpenSolaris, 9base, GNU+Ironclad, GNU(+Hurd), KolibriOS, etc, and given a new lease of life for another decade or two, and unlikely to ever suffer like it suffered under windows ever again…
No operating system will change your ancient laptop’s CPU to a more powerful and efficient one though. It’ll feel snappier to use because there are fewer background processes, but it won’t really be fast. Browsers will still be slow, so will code compilation, etc.
Oh absolutely. It’s running Ubuntu for a couple years now and it’s so much better.
I enjoy the backpack detection mode they have on laptops to make sure it turns on, overheats, and drains the battery anytime you take it somewhere you’ll want to use it unplugged.
Rip the power cord out of the wall
I just push the button.
Muhahahahaha.
Okay, sometimes on a whim I’ll do something like a “
sudo shutdown -t 0 now”. (… Muahahaha.)Rarely shutdown my main computers though. Last time, years ago.
Better to have, and not need, than to need, and not have, right windows users?
halt 0Don’t the -t 0 and now do the same thing?
I’ve stumbled into various quirks across many systems over the decades, and, iirc, it was actually something like
sudo shutdown -t secs now[(?! wat)] that resulted in reliable shutdown, contrary to all logic and presumed would-be redundancy. But, yeah, you’d think so. I don’t know what the current state of shutdown’s like. That was from like over 15 years ago, back when I had a X60T thinkpad I’d actually shutdown.
I’ve never used systemd to shut down
Sudo shutdown -h now works on the Mac
In most distros
shutdownis a symlink tosystemctl.Glad I don’t use “most distros”.
Gentoo baby!
Oh interesting
Huh.
I just use poweroff.
i dunno I just normally do sudo poweroff.
“shutdown” is a noun. I was on vacation because the company was in shutdown.
“shut down” is the compound verb you wanted.
Grammar checking a wojack meme?
Username checks out.
Username checks out.
must… not… bite…
I would argue executables can be verbified.
I can
grepa file. Why can’t ishutdown?Because grep isn’t a word? And since when do machines set the tone for human activity? Lights turn on, do you turn on in the morning?
🥴 I would 4 u bb
Systemd getting stuck on <random thing> on shutdown is one of the reasons i’ve ditched it.
“A stop job is running for user manager for UID 1000” is such a pain :D
You can change the default wait from 90 seconds to something like 5 seconds.
I don’t think I’ve ever had that issue. My PC shuts down within a few seconds. What kind of things would refuse to terminate?
a bad configuration, mostly. people love to bash systemd but this is sensible, that it does not outright kill services that aren’t ready for that. if your computer shuts diwn slowly because of that, that is a configuration issue, that either a service or a mount does not stop cleanly.
I solve that by holding my power button, not worth the hassle of ditching systemd for me
You could just configure the default timeout.
It’s even worse, when I tell my work Windows 11 computer to shut down and I have to choose update and shutdown because it decided to do updates, sometimes it reboots a few times but then it doesn’t turn off afterwards.
I’m never going to install Windows 11 on any of my devices, it’s so bad.
I bought a new mini PC the other day that shipped with windows 11. Before installing Linux I thought “I’ll just boot into windows to make sure the hardware is all correct”.
I got as far as the windows welcome screen and thought “it’s actually just going to be faster and easier to install Debian instead of going through all this windows bullshit”
I got a new Mini a month ago. Before I even powered it up, I stabbed a USB stick into it, hit escape on boot, and killed that bitch with Kinonite.
There are two things a person needs to do when starting up a fresh new computer: First, you must bathe in the purifying waters of Lake Minnetonka, and never, ever let Windows have even a single chance to live.
Or my old windows 10 machine would wake itself up in the middle of the night to run updates that the group policy wouldn’t even allow it to download without my permission and then just sit there. If I hadn’t fallen asleep yet, I’d notice the monitor light up the next room and get up swearing at Microsoft until I tracked down where the wakeup timer was set and disabled it. Only to find it re-enabled after some updates.
Fuck Microsoft.
It’s fun when your laptop decides to do this kind of nonsense from inside your laptop bag, smothering itself in its own heat.
I have a solution for this inside on my work computer. I put it on a Shelly plug. I tell homeassistant to power that on before my shift starts. When I shut down the computer at the end of my shift, the plug sees the drop in current draw and powers off that outlet.
The windows pc doesn’t even get power unless I want it to. It can starve.
