Signals SIGSTOP

[Nuno Almeida]

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 catch the SIGSTOP signal is this normal? Why the diference?   Waiting for someones explanation,   Nuno Almeida   @lwais at [EMAIL PROTECTED]