• BenjiRenji@feddit.org
      link
      fedilink
      arrow-up
      4
      ·
      4 hours ago

      Right. Sigterm should always be the first choice as a process may have the chance to handle that signal, free resources, save data etc. Sigkill pulls the rug out under it, which is a last resort, but may be necessary if the process can’t handle sigterm in reasonable time.

      So the meme basically shows these two signals, both Windows and different Linux distributions have different ways to when they send each signal and how the user can use them.

    • Natanox@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      10 hours ago

      Afaik KDE and Gnome do use SIGKILL at some point except for certain processes like running package managers. At least they are able to forcibly close almost anything if you really insist on shutting down now, depending on your (distro) configuration. Correct me if I’m wrong, but from my experience in Gnome you have to click on shutdown twice for it to happen, while KDE gives applications a 60 sec grace period unless you click a button in a notification pop-up.

      Edit: Not sure how it is in the terminal aside from those 1:30min grace periods during shutdown.

      • Phen@lemmy.eco.br
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        7 hours ago

        Are you telling me there’s a reason why I have to click shutdown twice for gnome to start the shutdown process? I always wondered why it had that 60s waiting time.

        • BCsven@lemmy.ca
          link
          fedilink
          arrow-up
          3
          ·
          2 hours ago

          The 60s is just a “oops I actually wanted to do X thing tbefore shudown”. So you don’t have to reboot for your forgotten task you meant to do