Reminds me of one of the truest comics I ever read.
Reminds me of one of the truest comics I ever read.
[**ββββ] 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)`
A stop job is running
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 2
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.
Alt-SysRq-i, u, o
I don't have time for this shit.
(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.
I've never used systemd to shut down
Sudo shutdown -h now works on the Mac
In most distros shutdown is a symlink to systemctl.
Just poweroff is fine. Why lose extra 2.5 seconds typing two words when one word will suffice?
What?
sync ; sync ; sync ; shutdown -h now
Or nothing!
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.
systemctl invariably hangs on waitimg for some job to finish. systemd-shutdown-inhibitor is hideous.
poweroff -ff
Everyone arguing about the amount of keypresses to type a shutdown command and time it takes to shutdown... I just power it off at the wall. One button press, shutdown is near instantaneous
Powers on
Immediately starts shut down
Refuses to close because the following programs are still running
The list is empty
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
You can just type "shutdown now" and it does.
it's now safe to turn off your computer
Not to be that guy but...
shutdown /s /f /t 0
Five seconds? What's hogging that system? Mine is about two, at most, from the WM shutdown selection.
Apparently there are a lot of ways to shutdown. halt is my preference from the command line.
I like shutdown now because it feels like I'm reprimanding my PC
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.
top 50 comments