Child processes being left behind is certainly an annoyance, but if they belong to something complex such as a dbms then you'll often need to clean them up in the correct order to avoid the risk of dataloss/corruption or other problems. Systemd blindly going "AH HA!... Orphaned processes!.... NUKE!!!!!!!!" isn't a silver bullet for this issue, and will likely just make matters worse.
cgroups have their uses, especially on larger systems where workload management is more important, but
- systemd is not required to use cgroups.
- their purpose is to provide resource allocation/management, not process tracking..
- They don't come for free: there is overhead associated with using them (just like with SELinux)
- And finally, parent processes should bloody well look after their children themselves, and having systemd intervene in a way that can only be likened to a Cyberdyne T-101's idea of a child welfare officer is simply approaching the problem from the wrong end.
But, none of this matters as Dietrich will probably just continue dancing his systemd is good, bad, good, bad, Okey Cokey. while the page-hits keep rolling in.
