this post was submitted on 04 Oct 2023
728 points (95.3% liked)

linuxmemes

20747 readers
891 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 49 points 11 months ago* (last edited 11 months ago) (5 children)

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?

[–] seaQueue 24 points 11 months ago* (last edited 11 months ago) (1 children)

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

[–] [email protected] 1 points 11 months ago (1 children)

That version is too new to be in any stable server distro yet.

[–] seaQueue 6 points 11 months ago

Ah, fair enough. I've used it on my Arch boxes since shortly after release.

[–] [email protected] 24 points 11 months ago

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

[–] elscallr 10 points 11 months ago

Raising Skinny Elephants Is Utterly Boring.

It can be done remotely, even over SSH by writing to /proc/sysrq-trigger

[–] whats_all_this_then 6 points 11 months ago (3 children)

I 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?

[–] orangeboats 5 points 11 months ago* (last edited 11 months ago)

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.

[–] [email protected] 4 points 11 months ago

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.

[–] [email protected] 3 points 11 months ago

I mean. You can fix those with a bit of effort.

[–] [email protected] 0 points 11 months ago

I want init 6 back! It's a reflex to type that.