Re: Program suddenly gets killed

From: Peter Jensen (usenet_at_pekajemaps.homeip.net)
Date: 09/17/04 

Date: 17 Sep 2004 13:23:36 GMT

Andrea Raimondi wrote:

> How about disabling SIG_KILL at the start of the most sensitive
> operations and re-enabling it at the end?

Snipped from the signal(7) manual page:

The signals SIGKILL and SIGSTOP cannot be caught, blocked, or ignored.

Makes sense, doesn't it? 

-- 
PeKaJe
You fill a much-needed gap.

Relevant Pages

  • Re: Program suddenly gets killed
    ... Andrea Raimondi wrote: ... >> The signals SIGKILL and SIGSTOP cannot be caught, blocked, or ignored. ...
    (alt.os.linux)
  • Re: I cant figure out how to trap ctrl-z/ctrl-c in the following
    ... SIGSTOP to be set to SIG_IGN. ... The system will not allow a process to catch the signals SIGKILL and ... If the ISIG flag is set, receipt of the SUSP character causes a SIGTSTP ... IXON (output control) or IXOFF flag is set. ...
    (comp.unix.programmer)
  • Re: SIGSTOP ignored?
    ... I wrote a script to send a SIGSTOP signal to that process ... However, after receiving SIGSTOP, the ... The system will not allow the action for the signals SIGKILL or SIGSTOP to be set to SIG_IGN. ...
    (comp.unix.programmer)