> The fact that the child doesn't want to send a signal to the parent on
> exit is a totally different matter, and should already be supported by
> just giving a zero signal number.
exit signal 0 is already being used and relied on by kmod - i originally
implemented it that way. In that case the child thread becomes a zombie
until the parent exits, and then it gets reparented to init. I did not
want to break any existing semantics (no matter how broken they appeared
to me) thus i introduced CLONE_DETACHED. But thinking about it, 'a zombie
staying around indefinitely' is not a semantics that it worth carrying too
far? But in case, if signal 0 is the preferred interface then i'm all for
it - this is not really a clone() property but an exit-signalling
property.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/