Systemd waiting for <random thing> to terminate on shutdown is one of the reasons i’ve ditched it.
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.
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)”
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
Windows update set my PC back almost 3 years for some unknown reason, lost so much shit. That was my final fuck it this shit moment, I installed Mint last week. A little bit of a learning curve, but I’m enjoying it and not worried about everything getting ruined unless I do something dumb. I can live with my own stupid.
You can just type “shutdown now” and it does.
Or just
poweroff, one word not two
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.
My button does the same as poweroff though, it will still give everything a couple seconds to kill itself
Well, there’s a reason why I shut down my Windows laptop at least 30 minutes before I have to actually leave somewhere.
My biggest annoyance isn’t even Windows as such, but random applications that have auto-updaters that run when the app is closed. “Okay, time to go now.” “NO! I must update this app!! Do not stop this update or hideously evil data corruption will happen!!!” …there’s no excuse for this stuff. Just do it when starting the application.
Rip the power cord out of the wall
[** ] 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
*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.
Who needs their files closed and disks synced, anyway?
I was just pointing out the irony of your statement. I think this is a low effort meme for sure
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…
Oh absolutely. It’s running Ubuntu for a couple years now and it’s so much better.
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.
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.
Maybe train you into avoiding shutdowns, never shutdown, stay on Microsoft windows for ever, forget about other things like sleep or eating.
Having a monopoly makes you arrogant. That is probably the only reason why they do it.
A stop job is runningWhy can’t it say what the job is 🧐🧐🧐
Actually, it usually does. I was just too lazy to think of one.
At 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.
Similar to angry parents.
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.
My always plugged in HDD with bees on it does that. 1 minute to shutdown at least because there’s always some kind of extend read or dedupe that need a sync.
… I brought this upon myself so I don’t have to complain.
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
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.
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. …]
