this post was submitted on 08 Sep 2024
400 points (99.0% liked)
linuxmemes
21172 readers
1954 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
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
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.
How did you get that from their sentence, what the fuck?