Am Mon, 2002-10-07 um 22.36 schrieb Michael Heironimus:
> On Mon, Oct 07, 2002 at 08:47:31PM +0200, Hugo van der Merwe wrote:
> > I noticed today that not everything responds to SIGTERM anymore...
> > SIGKILL, SIGSTOP and SIGCONT still work, but SIGTERM does not.. in some
> > cases.
>
> I don't know about the specific software you mention, but UNIX programs
> can install custom handlers or choose to drop some signals, like TERM. I
> think it's normal for login shells to ignore most signals.
maybe you can check signal(7) which describes all the signals under
linux including the default behavior. and of course the shell specific
man. e.g. for bash(1) there can be found:
SIGNALS
When bash is interactive, it ignores SIGTERM (so that kill
0 does not kill an interactive shell), and SIGINT is
caught and handled (so that the wait builtin is interrupt
ible). In all cases, bash ignores SIGQUIT. If job con
trol is in effect, bash ignores SIGTTIN, SIGTTOU, and
SIGTSTP.
cu
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
