this post was submitted on 04 Oct 2023
725 points (95.1% liked)
linuxmemes
21322 readers
926 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
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
sudoin 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!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
ya see, when i ssh into a server and i run some commands, sometimes i mess up, see, and i wanna reboot to get the system back to a known state, right
and even if the system is in an unknown or invalid state, right,
i don't wanna wait half a bloody hour for systemd to get tired of waiting for 1m30s countdowns and actually bounce the damn machine, if it bounces at all
and i can't just hold the power button, see, because i'm 2000 miles away from the bloody box
(I did not make that number up, by the way. I once has a hard drive get hot removed while it was mounted, couldn't umount it so I had to reboot, and it confused systemd so bad it took 27 minutes to shut down)
EDIT: aw come on, are you really gonna downvote without leaving a reply?
how is this any diffrent from SysV scripts hanging and preventing a reboot that way....
you are blaming SystemD for an issue not part of SystemD, but a generic computing issue...
and yes, you can still just hard reboot your system with SystemD as @[email protected] has point out....
Check out systemd's userspace reboot feature, they implemented it to avoid long reboot times on server hardware.
https://www.phoronix.com/news/systemd-254-Released
That version is too new to be in any stable server distro yet.
Ah, fair enough. I've used it on my Arch boxes since shortly after release.
Raising Skinny Elephants Is Utterly Boring.
It can be done remotely, even over SSH by writing to
/proc/sysrq-triggerI was wondering why my fedora install took ages to shutdown sometimes and the little googling I did got me nothing. Do i hate systemd now?
No, because that's not specific to systemd.
I can quite clearly remember the long shutdown times back when Ubuntu was still using Upstart.
Generally speaking, long shutdown times are an indication of a system issue (e.g. HDD going bad or slow network) or just scripts being written poorly, and could be worked around by changing the timeout value. Systemd defaults to 90 seconds, but you can change that to 30 secs or lower.
Heads up that you can hit [escape] key while booting or shutting down in order to see the console and tell what the computer is actually doing.
I mean. You can fix those with a bit of effort.
I want init 6 back! It's a reflex to type that.