Yes yes, I REALLY want to terminate that process and I am very sure about it too, ty.

  • Björn Tantau@swg-empire.de
    link
    fedilink
    arrow-up
    115
    ·
    8 hours ago

    And as always with this meme: Both Windows and Linux can ask a process nicely to terminate or kill it outright. And the default for both is to ask nicely.

    • WhyJiffie@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      3 hours ago

      on windows a process can get in a state so that it is impossible to make it go away, even with process explorer or process hacker. mostly this also involves the bugged software becoming unusable.

      I encounter such a situation from time to time. one way it could happen is if the USB controller has got in an invalid state, which one of my pendrives can semi-reliably reproduce. when that happens, any process attempting to deal with that device or its FS, even the built-in program to remove the drive letter, will stop working and hang as an unkillable process.

      • zea
        link
        fedilink
        arrow-up
        15
        ·
        3 hours ago

        Linux has that issue too. A process in an uninterruptible blocking syscall stays until that syscall finishes, which can be never if something weird’s going on.

      • Björn Tantau@swg-empire.de
        link
        fedilink
        arrow-up
        6
        ·
        edit-2
        3 hours ago

        I’ve seen that on Linux as well. Funnily enough also with faulty file systems. I think NFS with spotty wifi for one.

        Oh, and once with a dying RAID controller. That was a pain in the ass. At that point I swore to only ever do RAID in software.

        • WhyJiffie@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 hour ago

          oh yeah now that you say, SMB/CIFS mounted share if connection is no more. when I experienced this, it was temporary though, because there’s a timeout which is half (or double?) of the configurable reconnection timeout. but now that I think of it, I’m not sure if it made it unkillable.

      • linearchaos@lemmy.world
        link
        fedilink
        English
        arrow-up
        11
        ·
        4 hours ago

        Taskkill /f is reasonably close to sudo kill -9

        Hitting the X in Windows and hitting the X in Linux both cause the application to start a save yourself routine. From the OS standpoint they’re not far off.

        The problem is we have a lot of confirmation bias in windows because every time we want to close an application that’s not working, that save yourself call has to sit around for a hellaciously long time out followed by a telemetry call so that Microsoft can track that it happened.

        It’s pretty rare that Linux apps don’t just close.