GithubHelp home page GithubHelp logo

Comments (3)

HansKristian-Work avatar HansKristian-Work commented on July 3, 2024

They should receive SIGKILL. Is SIGKILL ignored for stopped processes? If so, then ye, that's an oversight ...

from fossilize.

kakra avatar kakra commented on July 3, 2024

It seems so: If I manually send SIGKILL to those, nothing happens until I send SIGCONT, and then those processes will instantly die if I sent SIGKILL previously. This is probably because SIGSTOP can be used for debugging: It stops the process, and won't get any more CPU cycles, thus it probably also doesn't receive the signal.

The comments in this question seem to suggest that you need to send SIGCONT so the SIGKILL signal sent previously can be received. After all, the process isn't killed from the outside, it will kill itself when it receives the signal.

Usually, SIGKILL should still kill the process because this signal cannot be blocked. But this answer suggests that - if you stop the process while in a kernel context - SIGKILL won't be delivered until it returns, so a SIGCONT would be needed. Maybe that's what happens? The other answers suggest that this can't properly tested or investigated from the shell.

Here's another link: https://unix.stackexchange.com/questions/298644/why-cant-i-kill-a-sigstopd-process-with-a-sigterm-and-where-is-the-pending-si/298650

The conclusion seems to be somewhat odd, some suggest that SIGKILL should kill a stopped process, others say it doesn't, and all the tests seem to confirm the first which some attribute to a bash bug. It looks like it is: Stopped processes cannot kill themselves until they continue.

from fossilize.

HansKristian-Work avatar HansKristian-Work commented on July 3, 2024

the higher level used SIGTERM instead of KILL which broke it. Another bug was that socketpair DGRAM doesn't work like I expected :V

from fossilize.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.