You must log in or # to comment.
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?
You can just type “shutdown now” and it does.
*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.
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?
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.
[** ] 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
Forgot this command! Gotta see if it’ll work on my system and not start a restart when I ask for a shutdown!
Edit:
I hope to high heaven it’s just an OS bug! Tried running this and the poweroff -ff commands and it just reboots my system! Now I am paranoid I somehow got a virus on my system!
It’s amazing that my pc is set to shut down when I press power button.
Not even “press and hold for a sec.” No I just press the power and by the time I lift my finger it’s already shutting down.
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”
But you don’t need to restart Linux for updates most of the time, basically just kernel updates, and those aren’t often done more than once a month or so, less for fixed point release distros
For most people, especially work computer/laptop users, making the update happen by default on restart or during sleep hours does a lot to keep the pc updated, because they would otherwise never do it themselves. There is a somewhat large minority of users who complain about such behaviour, but these are mostly people into computers anyways and can update their stuff anyways.
But the biggest gripe is the horrid implementation of the start menu power buttons in windows:
- update and restart: mostly works as you would expect - updates and boots the pc
- update and shutdown: updates the pc, and instead of leaving the pc in shutdown state, many times it just boots the pc again, working like update and restart
- restart/shutdown without updating: non-insignificant chance of it doing the update anyways
Thank you for mentioning the horrible implementation of the power button options.
Update and shutdown? Nah, I don’t feel like it. I’m gonna restart five times also and then I’m boot into Windows.
Reminds me of one of the truest comics I ever read.
A stop job is runningWhy can’t it say what the job is 🧐🧐🧐
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.
(X time / 1:30) but the second time will be extended indefinitely for some fucking reason.
Alt-SysRq-i, u, oI don’t have time for this shit.
have i learned a new magic combo?!
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
Shutdown NOW
Yes sir!
Y-
systemctl invariably hangs on waitimg for some job to finish.
systemd-shutdown-inhibitoris hideous.poweroff -ffWindows cannot shut down because there is a folder open.
Windows cannot shutdown because there’s a Windows open.
Is there a “How to Linux” somewhere? I’d really like to get beyond using my CachyOS system as gui user, hell even some of the gui stuff is so alien. Felt like a lesser god when I found the repo… But terminal commands are just beyond me
This helped me quite a lot. You don’t have to use arcolinux either, it’s simply a guide.
https://www.arcolinux.info/learning-path/
edit i haven’t used that link in awhile and i’m not sure it’s the same experience anymore, some things appear to be missing. if unsure about any step, you can skip it usually. it’s more of a list of things to learn.
Nothing wrong with GUI but yeah there are a lot of resources. I don’t know if I can point you to any because I usually just web search the command for the thing I want to do and add it to a long running note of Linux commands
Check out “Linux survival” if you’re old school, LabEx if you like experiential learning more, and less explanation. Both offer exercises, both are free, but Labex has a few restrictions for free accounts, and offers a paid tier at like 9 bucks a month. And ofc you don’t have to use the terminal irl, it’s just easier after getting used to it. Most things have a GUI program equivalent, you just have to seek it out. Most of the time.
Edit: And also, Linux Mint and a few others are often recommended to new users for being both similarish to windows and approachable with GUI.
Thank you! I’ve used mint, liked it, tried PopOS, had some trouble with it I can’t remember and instead of solving it moved to CachyOS which promised to solve the issue, and it did. I think it was Bluetooth
