• rumba@lemmy.zip
    link
    fedilink
    English
    arrow-up
    3
    ·
    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
        ·
        1 day 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
      6
      ·
      edit-2
      1 day 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
        3
        ·
        1 day 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
          3
          ·
          edit-2
          1 day 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
              13 hours 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
                ·
                13 hours 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 :)

    • mrgoosmoos@lemmy.ca
      link
      fedilink
      English
      arrow-up
      9
      ·
      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

    • JcbAzPx@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day 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.

  • AlsaValderaan@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    9
    ·
    2 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.

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

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

  • Squiddork@lemmy.world
    link
    fedilink
    arrow-up
    29
    arrow-down
    1
    ·
    edit-2
    3 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
      6
      ·
      2 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
        3
        ·
        edit-2
        2 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.

    • vithigar@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 day 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.

    • Quik@infosec.pub
      link
      fedilink
      arrow-up
      2
      ·
      17 hours ago

      This is so fucking annoying. Whenever you try to run something not clearly meant for the desktop, there is like a 80/20 chance that you can completely forget suspend…

    • ragas@lemmy.ml
      link
      fedilink
      arrow-up
      7
      ·
      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.)

      • Successful_Try543@feddit.org
        link
        fedilink
        arrow-up
        5
        ·
        3 days ago

        I do “;” to definitely run the shutdown after the update process exits.

        If you’re able to successfully boot the machine afterwards is not your concern?

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

          I don’t know about arch but my system usually boots fine after an upgrade. (Gentoo here)

              • Successful_Try543@feddit.org
                link
                fedilink
                arrow-up
                1
                ·
                2 days ago

                No. It will boot the previous kernel, but the user experience will be at least suboptimal if some packages have already been removed during the upgrade, but the upgrade stopped at some point because a downloaded package was corrupt, leaving lots of dependent packages unconfigured. In case networking doesn’t work, it’s also inconvenient to manually download the affected package on another machine and transfer it with a usb stick onto the computer to restart the upgrade.

    • baltakatei@sopuli.xyz
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      3 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
        4
        ·
        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
          2
          ·
          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.

      • Successful_Try543@feddit.org
        link
        fedilink
        arrow-up
        5
        ·
        edit-2
        3 days ago

        Yes, in this command one liner, the system should not power off when the update took too long.

        Or is yes somehow supposed to take care of this?

        No, yes is simply answering all questions asked during the update procedure (start upgrade, replace config files, restart services) with “yes”.

        • somerandomperson@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          3 days ago

          There’s no timeout for sudo. When permitted, a process runs as root and then closes.

          Also, the system will still shutdown when update fails because pipes do not care if previous commands exit with a nonzero code, unless pipefail is set.

          Edit: i’m blind.