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)”
Systemd waiting for <random thing> to terminate on shutdown is one of the reasons i’ve ditched it.
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.
“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
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 2
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.
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 process 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.
You can just type “shutdown now” and it does.
Or just
poweroff, one word not two
You know I’m okay with Windows running updates I shut down or anything else like that. It’s incredibly annoying when people don’t run updates and then wonder why their system gets fucked up. It’s just like on Linux when people just absolutely refuse to acknowledge the fact that they need to run updates. And many times I need to run the updates manually through the command line. There are quite a few gooey applications and things like that that will allow you to run updates but many times you still have to run them manually. And then something breaks and people wonder why I broke when they didn’t run any updates. So in the end really who gives a fuck if it’s running updates on shutdown you hit the button says run updates you tell it to run updates and you either close the lid on your laptop and walk away or you carry it till it shuts down within a few minutes and then you shut it down. Or you just let your desktop run until it’s done. It’s really not that big of a deal that people here seem to make it out to be and seem to make 10 different memes a day about the shutdown process on whatever OS they want to shut down.
The problem is how they install the fucking updates.
“OMG IT’S PATCH TUESDAY!!!11111!! NEEED TO REBOOT IMMEDIATELY RIGHT NOW I MUST FORCE CLOSE ALL THE OPEN APPLICATIONS WITHOUT SAVING ANY WORK, THE USER GONNA APPRECIATE THAT”
I mean it’s not really horrible it’s actually a pretty good idea for people that either a are not computer savvy or b wouldn’t normally update without being reminded to do stuff like that. Which unfortunately for people like you and I is the vast majority of people in you know the world. Actual computer users who understand and can do it on their own are very few and far between. Think about an average company of say 5,000 people and that’s a small fish company. There’s an it department of what maybe 10 to 15 if that. And in that case you may be have another 20 users maybe 30 users total that have any knowledge of computers at all. That’s a huge amount of people right there in a huge amount of computers that would never have any updates for patches and become vulnerable to everything from crashing to getting hacked. Without those automatic upd
[** ] 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)`
Just
poweroffis fine. Why lose extra 2.5 seconds typing two words when one word will suffice?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.
