SIGKILL is unblockable in Unix. There is a lot of logic to that. X can choose
to become totally setuid if it wishes. The ongoing fbcon/KGI work fixes
this problem the right way
> are able to send few fignals (that generated from
> keyboard). Alternatively, we might want to defend against SIGKILL only
> - everything else may be catched...
SIGKILL should never ever be blocked. Its the 'get out of mess' button.
> > Your code also appears to have broken signal delivery to processes that
> > are setuid and depend on it (such as rlogind).
>
> What signals need to be delivered to rlogind?
SIGURG, and maybe SIGIO
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu