> Uh ? It should be already de-POSIXed. For "regular" processes,
> SIGOVERKILL should probably just act like SIGKILL. Still leaves the
> issue that tools to kill processes may need to know about the new
> signal too.
Numerous apps rely on knowing SIGKILL kills stuff dead. This hack is simply
uglier than handling these few special cases.
Lets be honest SIGSTOP and SIGKILL are not critical fast paths for signals
and with the thread group id Linus proposed we have a chain of tasks for the
thread group so we are talking about adding a chain of code to signal a
thread group that only has to deal with a few signals
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 21:00:14 EST