Messages in this thread | | | From | Roland McGrath <> | Subject | Re: [PATCH] exit: PR_SET_ANCHOR for marking processes as reapers for child processes | Date | Fri, 5 Mar 2010 11:18:16 -0800 (PST) |
| |
> Oh, no. Actually getting the SIGCHILD is the needed feature here. A > process who sets the ANCHOR flag is surely expected to handle these > signals. It's all about a user "init-like" process" that can do > similar things for a logged-in user what /sbin/init can to for the > system. So, it's all about 1.), and 3.) is a nice side-effect, but not > the motivation to do this.
Please explain this more explicitly. What the actual init does with miscellaneous reparented processes is just reap them and ignore their status. What do you intend an "anchor" process to do other than that?
Thanks, Roland
| |