• rumba@lemmy.zip
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 days ago

    for the most part i don’t care, but really, all those fucking terminals i left open, i know they’re open, that click per window of yes close has never been helpful

      • rumba@lemmy.zip
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 days ago

        I bet there were interesting uses.

        I won’t say i’ve never shut down a long running process, but i’ve gotten a lot better at not running them adhoc in a terminal :)

    • Sabata@ani.social
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      2 days ago

      The program ‘btop’ is currently running in this session. Are you sure you want to close it?

      • rumba@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 days ago

        i’ll prob just start running pkill konsole before shutdown. was thinking of pkexec /sbin/shutdown -h now on a button, but it is kind of nice having some of my apps recover on reboot.

        • Sabata@ani.social
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          2 days ago

          I just don’t shutdown until I get a big backlog of updates. I have to remount my SSD with my games on it every time, then tell steam.

            • Sabata@ani.social
              link
              fedilink
              arrow-up
              2
              ·
              edit-2
              1 day ago

              I blew up the OS a few times doing that wrong. I’ll just hit the mount button. Good enough.

              • 𝕛𝕨𝕞-𝕕𝕖𝕧@lemmy.dbzer0.com
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 day ago

                it’s real easy. if you tell me your distro and send me your lsblk output when it’s setup how you like i can send you what to put in fstab to persist it. better for system management, better for the puter. gotta reboot more often :)

    • JcbAzPx@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 days ago

      Shutdown isn’t shutdown anymore, so it has to reboot for the updates. After the reboot, though, there’s no longer a shutdown pending.

  • JATth@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 days ago

    Just do sysrq+s, sysrq+c (triggers panic) and flip the power switch for instant power off.

    • mrgoosmoos@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      one of the reasons I’m moving away. pisses me off so much at work, I don’t even want it at home

    • vithigar@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      2 days ago

      It’s much less risky than it used to be. Journaling filesystems reduce the risk of filesystem corruption to near zero and are fairly ubiquitous now on non-removable media.

  • AlsaValderaan@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    1
    ·
    3 days ago

    On my work PC I disabled automatic restarts and I’ll just hibernate it for weeks at a time, keeping my work stuff open. Convenient, and I can install updates when I choose to.

  • Squiddork@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    4 days ago

    Managed to wreck my NVMe drive with an unsafe shutdown on linux the other week, gave it a few hours for the self check, booted back into the distro and has been running fine ever since.

    Pretty sure windows would’ve just set the computer on fire at this point.

    • LordAmplifier@pawb.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      That’s weak. I always pull on the power cord until the plug comes out. That shuts it down in a second flat.

      • Avid Amoeba@lemmy.ca
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        3 days ago

        I was talking about a laptop with non-removable battery of course! I turn off my desktop via Zigbee remote hooked to Home Assistant which flips a Zigbee power switch that the AC power cord is hooked up to. Even faster death than going under the desk and unplugging the power cord. Even just unplugging itself takes time.

    • ragas@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      3 days ago

      “&&” will only run shutdown if the update runs correctly.

      I do “;” to definitely run the shutdown after the update process exits. (Don’t want to keep the system running if nothing is happening any more.)

    • baltakatei@sopuli.xyz
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      4 days ago

      Assuming you enter your password upon running sudo, isn’t there the risk of sudo’s privilege timing out if pacman takes too long to complete? I believe I tried something similar, intending to run a one-liner I could start then walk away from. However, I ended up returning to see the system not rebooted hours later.

      Or is yes somehow supposed to take care of this? Sorry, newish Debian user here who hasn’t ventured outside the distribution much.

      • Matriks404@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        3 days ago

        The command after && runs only if the previous command returns non-error exit status (0), if pacman returns error the latter command won’t be executed.

        Additionally there’s probably a configuration option for sudo for it to not time out, but it doesn’t matter since you can just use systemctl reboot as a normal user to reboot your system (at least on Debian). If that’s too long I recommend to add this to your .bashrc (if you use Bash): alias reb='systemctl reboot' or something similar.

        • Ziglin (it/they)@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 days ago

          Maybe this is just a yay thing but I think if sudo priveleges run out while downloading the files it prompts you for your password again before performing the changes. That would lead to it either trying to use the yes output or getting stuck in the password prompt, only failing in the prior.

          This entire problem could be solved by just running it as the root user.