Re: [PATCH] exit: PR_SET_ANCHOR for marking processes as reapers for child processes
From: Roland McGrath
Date: Fri Mar 05 2010 - 14:19:37 EST
> 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?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/