Timeline for Why does SIGINT not terminate a stopped process?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S May 16, 2022 at 15:10 | history | edited | Stephen Kitt | CC BY-SA 4.0 |
Better key formatting.
|
| S May 16, 2022 at 15:10 | history | suggested | Manuel Jordan | CC BY-SA 4.0 |
Improve presentation
|
| May 16, 2022 at 14:30 | review | Suggested edits | |||
| S May 16, 2022 at 15:10 | |||||
| S Nov 23, 2020 at 20:26 | history | suggested | mateleco | CC BY-SA 4.0 |
Pointed out that the signal SIGINT will be unblocked after SIGCONT is received.
|
| Nov 22, 2020 at 16:30 | comment | added | mateleco |
Thanks. That makes a lot of sense, because when I execute kill -SIGCONT pid, SIGINT gets unblocked and the pending SIGINT signal is delivered, causing the process to terminate.
|
|
| Nov 22, 2020 at 16:23 | vote | accept | mateleco | ||
| Nov 22, 2020 at 16:23 | review | Suggested edits | |||
| S Nov 23, 2020 at 20:26 | |||||
| Nov 22, 2020 at 5:06 | history | answered | Meow | CC BY-SA 4.0 |