reupload because i mixed up sigterm and sigkill like a dumb fuck

  • eighty@aussie.zoneEnglish
    0·
    1 month ago

    It’s tragic the level of immediate relief I feel every time I shutdown on Linux after years on Windows.

    • Sanguine@lemmy.dbzer0.comEnglish
      0·
      1 month ago

      Maybe something I don’t know, but I send kill commands through btop all the time on a systemd based machine.

      • Ooops@feddit.org
        0·
        1 month ago

        The point here is that SystemD’s natural behavior is to send SIGTERM then wait an eternity.

        Those “service XY is shutting down (5sec/2min)” messages you sometimes get on shutdown are coming from SystemD not waiting for 3 seconds like the meme suggests, but waiting for minutes before giving up and switching over to SIGKILL instead.

          • Ooops@feddit.org
            0·
            19 days ago

            There is the option to explicitly set DefaultTimeoutStartSec and DefaultTimeoutStopSec per systemd service.

            If you don’t specify it in a service file, the default values from /etc/systemd/system.conf (both set to 90s) will be used, so you can change those values to 30s, too, to affect all services (that don’t have their limit set explicitly) globally.

  • Get_Off_My_WLAN@fedia.io
    0·
    1 month ago

    I had to update a Windows 11 work laptop after not touching it for nearly a year. I click ‘shut down’ from the start menu and nothing happens. What? Try it again. Nothing again.

    I have to hold down the power button before the screen shows a “slide to shut down” screen now. How did Microslop fuck up the ‘shut down’ so badly.

    • hexagonwin@lemmy.today
      0·
      29 days ago

      the alt f4 shutdown window present since win95/nt4 tends to work better than the latest slop menu they made

    • chiliedogg@lemmy.world
      0·
      1 month ago

      I love how the design is so bad now we’re missing the days when shutting down the computer required the “Start” button.

  • Wispy2891@lemmy.world
    0·
    1 month ago

    Reverse meme when it’s time to install the updates.

    Windows in that case is “I MUST REBOOT IMMEDIATELY PREPARE TO LOSE ALL UNSAVED DATA IN 3. 2. 1…”

    • Buddahriffic@lemmy.world
      0·
      1 month ago

      When I switched to win 10, I actually gave them more money to get the pro version for access to the group policy editor so I could control updates and never have to deal with my PC telling me it’s time to restart on its own. Because I was stupid.

      When it came time to switch to Win 11, I did the much more sensible thing and installed Fedora instead. I started with cinnamon and even though I ended up disliking it also, it was still way better than the windows experience.

    • Trail@lemmy.world
      0·
      30 days ago

      Not quite. I will RESUME FROM THIS FUCKING “MODERN SLEEP” shit, even though you the user want to turn this shit right off, do it without any warning watsoever, close all your fucking windows and good luck if you have lost work or not.

  • Quacksalber@sh.itjust.works
    0·
    1 month ago

    I prefer Windows giving programs time to shut down properly. You can always click on ‘shutdown anyways’ or whatever the button is called. Also what kind of programs do you run that take 45 seconds to shut down?

    • Björn@swg-empire.de
      0·
      1 month ago

      That’s actually the default on Linux as well. This meme just gets shared every other week, perpetuating the myth. OP seems to be aware of that.

    • Miaou@jlai.lu
      0·
      1 month ago

      It doesn’t “give time” it just waits indefinitely, and if the program doesn’t terminate your laptop will just sit there until the battery dies. This has to be one of the dumbest aspect of Windows, and god knows there are many

    • sem@piefed.blahaj.zoneEnglish
      0·
      30 days ago

      I guess the difference is that sigterm usually closes all the programs pretty quickly; but ITT I am learning that is not always the case!

    • DaforLynx@lemmy.zipEnglish
      0·
      1 month ago

      How do you configure this? I have often encountered minute-long restarts most of which was fixed by adding a service to kill the wine server on shutdown, but still it sometimes happens.

  • Demdaru@lemmy.worldEnglish
    0·
    29 days ago

    Gonna make Lemmy pissed off, but installed on my machine Nobara, Cachy and Mint at some point. All of them had comparable if not worse boot and shutdown times to Windows 10. xD ( And worse performance in games but that’s due to having old Nvidia GPU xD )

        • RustyNova@lemmy.world
          0·
          1 month ago

          In those cases there’s an easy solution.

          Step 1: sigh

          Step 2: press the power button 5 or 10 seconds while contemplating why you decided to do a quick restart instead of keeping the session and do something actually productive

          • KubeRoot@discuss.tchncs.deEnglish
            0·
            1 month ago

            I recommend starting with SysRq+E before that, there’s a chance it gets whatever the shutdown was waiting for. And if that fails… REISUB my beloved.

              • KubeRoot@discuss.tchncs.deEnglish
                0·
                29 days ago

                I might be missing something, but the order I know and have always seen recommended is REISUB. Terminating processes might write data to disk, so it seems to me like you should sync after, not before. Though this is also generally unimportant with modern filesystems and storage media.

      • RustyNova@lemmy.world
        0·
        1 month ago

        That’s because it first send sigterm, then sigkill. Then it gives up and let the kernel handle it…

        Happens on my BTRFS disk’s unmount. If the kernel is currently busy handling some heavy btrfs command (like a 4tb scrub), systemd cannot stop it with sigkill.

        So when it eventually gives up, you also need to wait for the kernel to finally stop the operation and actually disconnect the disk.

  • CosmoNova@lemmy.world
    0·
    1 month ago

    Ironic. Because a bug on CachyOS KDE made the shut down button in the quick menu disappear. Nobody in their community could help me or explain why. Generally I would say support is rather spotty with CachyOS in general. Of course you can shut it down in many other ways but that was my preferred one. So I just lived with it and instead used ctrl+alt+delete for a while until the button magically returned one day.

    • FatVegan@leminal.space
      0·
      1 month ago

      I’m kind of a linux noob, and i currently run catchyos and there are some things i don’t really understand. Last time i used linux is like 10 years ago, and i read and experienced that a really big plus on linux compared to windows is that you don’t need to restart when yoj install or update, but on catchy, you need to restart almost every update, which is almost every day it seems. Another thing that puzzles me is that every now and then, i restart for the update and wander off, and when i come back i don’t use the pc anymore and want to shut it down, but in the log in screen there is no shut down button, just a restart button.

      • KubeRoot@discuss.tchncs.deEnglish
        0·
        1 month ago

        I use Arch personally, and as mentioned you should restart every update - but you can just not update everyday (updates don’t even come at a scheduled time, it’s just packages getting new versions whenever, so by the time you finish updating there could be another updated package for you)

        I think updating weekly and as necessary is a good schedule, though if you don’t update frequently and try to install something new, the version pacman will try to install will be based on your local repository information, matched to your other packages, and might no longer be available in mirrors. And you shouldn’t install an updated version of just one package, because if it pulls in the wrong updated dependencies you could break your install.

      • Barbarian@sh.itjust.works
        0·
        1 month ago

        In general, it’s true that Linux doesn’t need to restart for most updates. However, if you get a power cut right in the middle of an update, that could leave your OS in a really bad state. Therefore, for safety reasons, some distros (apparently including CachyOS) do updates in a ‘safe mode’ on boot, so that if there’s a power cut it just rolls back cleanly.

        In short, how exactly distros approach updates differ slightly. A tradeoff between safety and convenience.