• AVincentInSpace@pawb.social
    link
    fedilink
    arrow-up
    38
    arrow-down
    8
    ·
    edit-2
    1 year ago

    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?

    • Sysosmaster@infosec.pub
      link
      fedilink
      English
      arrow-up
      19
      ·
      1 year 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 @elscallr@lemmy.world has point out…

    • whats_all_this_then@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      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?

      • rivalary@lemmy.ca
        link
        fedilink
        arrow-up
        4
        ·
        1 year 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.