You must log in or register to comment.
I have a, honest to goodness breaks the electron flow, power switch for a reason, the shutdown command was a warning not a request.
the shutdown command was a warning not a request.
Such wise words.
Love it or loathe it, systemctl is trying to do the right thing with regard to stability and data preservation.
If you really mean it, the manual offers a few levels of strength beyond the plain one:
-i(don’t check for busy processes, which is what’s going on in the meme),-f(force, presumably asks even less nicely), and-f -f(don’t even ask, just do it now, preservation be damned).It should give you the option to abort the shutdown and sort out whatever process it is though! Or at least let you kill it manually from the shutdown terminal. I know you can technically do that with the emergency shell but I don’t like leaving that enabled. Thankfully I rarely get this issue anymore anyway
systemctl is trying to do the right thing
I love how this comment suggests every fucking alternative doesn’t or wouldn’t. That’s just bloody arrogance.
Systemd’s entire existence is against best coding practice. Famously, when called out just on the ability to work with others, the systemd team represented trends ably.
Never have I raged at a machine and demanded it tell me what the flying flaming fuck it was actually doing now than when systemd was trying to do what I’m charitably deciding is the right thing.
Why would be doing the right thing now? It honestly only does a thing through luck and race conditions anyway.
I’m not sure I’m a fan of systemctl either, but I think your hatred of it has caused you to read way too much into what I said.
You can do that to Windows. They may have gotten better, but I know that my friend that ran Debian Unstable back in the late '90s-'00s swore that if he didn’t properly shut down the machine every year or so, it would mess up his build.
ps -ax -o pid | xargs kill -9I feel the same way when I use my turn signals. I’m not asking.
(assuming of course it’s safe to follow through)
$ poweroffkernel panics for some reason
have to use the power switch anyway
Such is life when using Linux on a laptop.
I’ve recently had so many random freezes of the system, hangs on shutdown, panics on shutdown, freezes in system updates, that hard reset became a thing I did several times a day. Yet there were no systemd logs, nothing in dmesg, literally zero information on what happened.
I was skeptical in blaming Nvidia because at this point it became a Linux chiche, but then I started to switch to integrated graphics (disabling dGPU) and all of the problems miraculously went away.
Same. I use nVidia on Wayland, and experience more crashes and panics than when using the iGPU. With older versions of the driver, I could consistently trigger a crash when exiting an app which used the discrete GPU (such as Steam), or by switching between a game and Firefox.
Had this issue for ages. Ditched Nvidia a month ago and now everything just works.
Why does that even happen?
The kernel is cleaning the corpses out of the basement freezer chest before the power goes out and stinks up the place.
Leave the poor kernel out of it, it has nothing to do with this. It’s Lennart, not Linus.
Unmounting CIFS , 1:30 timeout ! I just wannatgo to bed…
I was glad my server did this the other day to make sure the data Lemmy put into my database is secure.
Meh, init 6, you coward
kill -9 1
Still faster than Windows
