561
Killer (sh.itjust.works)
submitted 9 months ago by to c/linuxmemes@lemmy.world
45 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 94 points 9 months ago (12 children)

Ah, kill -9. Me old pal. Always ready to assist when inconvenient bodies needs to be buried out back. Best friend ever.

  • permalink
  • fedilink
  • source
  • hideshow 12 child comments
    •
  • [–] 77 points 9 months ago (3 children)

    Respect my -15, or I'll be back with my -9

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 4 points 9 months ago (2 children)

    Have you ever dealt with zombie processes?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 9 months ago

    At least those eat no resources besides taking up space in htop. And can be traced to the parent being weird.
    Have you dealt with io-locked processes? Funny D-statuses spreading like a disease, anything that touches an infected process or resource also inherits it. Worst cases I have seen (nfs client kernel module not connecting a mountpoint properly) made every one of those fully resistant to -9.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 9 months ago

    Doesn’t do much if the process is in uninterruptible I/o. Kill can’t do much against syscalls that aren’t returning, you’ll be rebooting. You can try this https://github.com/mitchty/nix/blob/shenanigans/src/evilkill.sh but it’s not guaranteed to work. It’s just trying to force the process to exit(), but it doesn’t always work and can’t. All that script amounts to is attaching a debugger and executing assembly to mimic exit. I’ll say 60% of the time it works 100% of the time when kill doesn’t.

  • permalink
  • fedilink
  • source
  • parent