News for hackers. Stuff that matters.
Re:Ghosts of Unix past, part 3: Unfixable designs (2010) by hnarn on Monday May 17, 2021 @02:39PM (#27186625)
This might be naive of me, but isn't this in a way fixed by systemd service handling? Assuming the process in question is, in fact, handled as a service of course.
Re:Ghosts of Unix past, part 3: Unfixable designs (2010) by zxzax on Monday May 17, 2021 @03:22PM (#27187229)
The issue is solved in any service manager as long as the service doesn't fork, when you are the parent process you can ensure that you don't reap the child before sending a signal.

Once the service forks then it becomes a problem. If you use cgroups it can be solved separately with the cgroup freezer, but there are still some open issues with this in systemd: https://github.com/systemd/systemd/issues/13101

Re:Ghosts of Unix past, part 3: Unfixable designs (2010) by Quekid5 on Monday May 17, 2021 @02:47PM (#27186734)
Correct.