Re: [RFC][PATCH] Notify init when processes are reparented to it

[Oleg Nesterov]

On 12/29, Scott James Remnant wrote:
>
> On Sun, 2008-12-28 at 14:01 -0800, Roland McGrath wrote:
>
> > I'm highly skeptical that this is a desireable feature at all, and
> > certainly I find the abuse of siginfo_t.si_status here extremely
> > questionable.  I think we need a clear explanation of what problems
> > the feature is intended to address.
> >
> Did the original e-mail not address this?

Do you mean

	[RFC] Notify init when processes are reparented to it
	http://marc.info/?l=linux-kernel&m=123038049428388

?

I am not sure I really understand the problem. And thus I can't
understand how this patch can help.

OK,

> We want to be able to supervise daemons.

What do you mean?

> Later on, 1002 will die and init will receive SIGCHLD for it.
>
> Unfortunately neither the 1001 or 1002 processes are known to init, even
> though they are original children of the process it spawned (1000), for
> init to be notified about them - this has been forgotten.

Ok, with this patch /sbin/init knows that 1002 is a descendant
of apache(1000) which was spwaned by init. What can init do
with this info?

To clarify, I am not arguing, I am just trying to understand.

Oleg.

--
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/