Timeline for Elegantly get list of descendant processes
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 28, 2022 at 0:21 | comment | added | Brandon | For anyone coming across this in 2022, these days the most sure-fire way to clean up all child processes is to use a PID namespace and then kill all processes in the namespace (and the easiest way to do that is to use something like a Docker or Podman container, and kill the whole container with --force). Killing by process group does not work if one of the child processes in the group decides to fork off into its own process group. | |
| Sep 29, 2015 at 19:17 | review | Late answers | |||
| Sep 29, 2015 at 19:36 | |||||
| Sep 13, 2013 at 13:58 | comment | added | AnotherSmellyGeek | In that case, I'm with @Gilles and @Jander; process groups are the best way. | |
| Jul 17, 2013 at 11:55 | comment | added | STenyaK | Both use cases are used in a continuous integration/testing environment, so they have to deal with the possibility of a bug existing in the child process/es. This bug may manifest itself as inability to properly shutdown themselves or their children, so I need a way to ensure that I can close them all in the worst case. | |
| Jul 14, 2013 at 15:54 | history | answered | AnotherSmellyGeek | CC BY-SA 3.0 |