A stop job is running

Five seconds? What's hogging that system? Mine is about two, at most, from the WM shutdown selection.

Alt-SysRq-i, u, o

I don't have time for this shit.

have i learned a new magic combo?!

At least it tells you how long it'll take before it decides to SIGKILL whatever is holding the shutdown sequence.

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!

Just alias whatever to "off"

Well you say that, but I've seen the countdown go past and then reset to a higher number often.

Poor storage drives adding on power cycles

I've never used systemd to shut down

Sudo shutdown -h now works on the Mac

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

meanwhile on KDE: A stop job is running

why?

Gotta make sure the FS cache syncs.

Not too sure, hence the use of semicolons instead of double ampersands, but a moderately high level of sure.

In most distros shutdown is a symlink to systemctl.

(X time / 1:30) but the second time will be extended indefinitely for some fucking reason.

Oh interesting

Windows cannot shut down because there is a folder open.

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

It's traditional, it used to be done that way on old systems. It was done for extra luck I suppose.

Nowadays, shutdown syncs as a matter of fact, and filesystems are much less brittle.

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.

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

Big brain move

I think doing just a poweroff might leave some services in an unclean state. I think systemctl poweroff make sure the services are shutdown cleanly before powering down.

Similar to angry parents.

People give Windows a lot of flak for this, but at least it usually does turn off after finishing its updates.

MacOS is the one that will just literally ignore the fact that you told it to shut down. Or it takes forever to tell you that a program has unsaved changes. At least Windows will tell you that right away, so that you see the "something is preventing shutdown" message before you walk away from the computer. Your Mac will wait 15 minutes, and then be like, "by the way, the browser doesn't want to close."

Reminds me of one of the truest comics I ever read.

3 syncs? Sun Microsystems trainers told me 2!

Seems risky to me...

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.

Before Linux had a shutdown command, you’d run “sync && sync && sync” then hit the power button.

I just use poweroff.

I entrust you with this horror, go figure out what to blame.

#! /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

Individual services can override the default 90 seconds timeout. But then you can override their override if you think you are smarter, of course.

If that one thumb could read, this might make him mad

"Update and Shutdown" still acts as "Update and Restart" on windows. They added a whole new feature that is indistinguishable from the previous feature.

Though I agree macos has the problem of "well Firefox was open so I was stuck here over night"

I usually map the power button to shut down, although on laptop if I close the screen after shutdown it'll go to sleep mid shutdown

Thanks, 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.

I get annoyed when a stop job shows up and I have to wait a minute. On my windows machines, that minute is the baseline and I half expect it to have decided to update and reboot itself again after. The difference is night and day

why use many word when few word do trick

You guys turn off your computers?

Systemctl?
Bro just poweroff

is that true? i guess it makes sense. you dont "shutdown" DOS

systemctl invariably hangs on waitimg for some job to finish. systemd-shutdown-inhibitor is hideous.

poweroff -ff

Not to be that guy but...

shutdown /s /f /t 0

I don't know how but a windows 7 machine I've recently had to use still got an update before shutting down...

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. Check man 8 systemd-shutdown for more info on that.

They fixed that behavior recently.