nd 17, for SIGKILL
> and SIGSTOP.
> On Debian I can catch the SIGSTOP signal is this normal? Why the diference?
Nothing can trap SIGKILL. Elsewise, how could anything be killed for
sure?
I'm not really familiar with SIGSTOP. But let me check... (snips from
man
below).
Looks like it
I would like to know if this is simply a singularity of Debian, or if it's a
bug of mine.
When I'm programming in C/C++ to other linux distr. and I make a signal trap
I can't, and that's absolutly normal, trap the signals 9 and 17, for SIGKILL
and SIGSTOP.
On Debian I can catc
2 matches
Mail list logo
