Powers on
Immediately starts shut down
Refuses to close because the following programs are still running
The list is empty
it’s now safe to turn off your computer
deleted by creator
“shutdown” is a noun. I was on vacation because the company was in shutdown.
“shut down” is the compound verb you wanted.
I would argue executables can be verbified.
I can
grepa file. Why can’t ishutdown?Grammar checking a wojack meme?
Username checks out.
Username checks out.
must… not… bite…
script on desktop; shutdown -h now, or hit button
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.
Makes me wonder how many laptops seemed to randomly get bricked because it tried to update but then ran out of battery in the middle of it but the user just sees that their laptop had no battery left and then won’t boot properly after that, never realizing it decided to update itself.
This boils down to a Linux using a file system which allows files to be deleted or replaced in the inode table while something has the old file open. So it’s easier (although not simple) to replace packages while other stuff is running. Whereas Windows has to shut everything else down so nothing has the file open to replace it and also fix stragglers during the next reboot.
its more to do with the fact that until recently linux distros did not have a desktop pc centered idea on how to do updates. but distros started to support offline updates, so you can install updates in a safer way, while the system is not running.
a major difference is that linux offline updates allows you to just shut down, without taking time with updates.
My phone and Linux PC’s now all do this. Primary partition in use. Updates apply to secondary partition. At next reboot, load the updated partition.
It’s so much better that the alternative, I can’t wait for Windows 14 to adopt it.
only atomic distros do that, and it has its downsides. most distros still only keep a single system partition, but if it does snapshots before update then it’s not a big deal if something goes wrong
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 /sYeah, 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 have an old laptop with a w7 partition for running some old cracked software. It has never seen a shitdown, only battery pulls. Not even the warning of a long press
My god that poor machine
“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
[** ] 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
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.
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.
Why can’t it say what the job is 🧐🧐🧐
Actually, it usually does. I was just too lazy to think of one.
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
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.
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.
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.
Systemd waiting for <random thing> to terminate 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.
/etc/systemd/system.conf.d/system.conf
[Manager] DefaultTimeoutStopSec=2s
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.
Udev i think. Also, that’s a thing Systemd is (more or less) infamous for. Which is, why this joke weirded me out a bit.
Also, that’s a thing Systemd is (more or less) infamous for.
I’ve never heard of it before. I don’t know where it is infamous, I’ve never had that issue and of all the criticism I’ve seen levelled at Linux in general or systemd in particular, that has never been one. Maybe there was some configuration stuff, as the other reply mentioned?
You could just configure the default timeout.
2 min is still a bit much for a default. Make it 10 seconds.
I solve that by holding my power button, not worth the hassle of ditching systemd for me
You can just type “shutdown now” and it does.
Or just
poweroff, one word not twoHow about
haltI just tried it but it gave me an error
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.
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.
