OK yeah I get that. Back in the day you used to we used to processes like containers. The system programmer would write the process executables or at least a pr

OK yeah I get that. Back in the day you used to we used to processes like containers. The system programmer would write the process executables or at least a process manager. If a process ever called setpgrp itself it did it for a controlled reason and because it was supposed to. You were in control of that because you wrote it so it's a non problem. In modern times wer'e doing more thing like containerizing a bunch of processes they are weakly related instead of using a VM for that so the use case became more pressing. There is cgroups for managing such a group of processes. I'm suprised to learn there is no way to reliably send a signal to all processes in a cgroup though. > SIGKILL will actually leave lots of orphans around instead of cleaning everything. Well actually orphan processes exist for a reason. Your supposed to "wait" / reap them to make them non orphan.