Re: 'crafty' took ages to kill
From: Frank Cusack (fcusack_at_fcusack.com)
Date: 12/31/03
- Next message: uboat2001: "boot cdrom failed - Can't read disk label"
- Previous message: Robb Ottenhoff: "Re: I can not su to root on my Sun Solaris 9 (SPARC) box, even with the correct password"
- In reply to: Ian Fitchet: "Re: 'crafty' took ages to kill"
- Next in thread: Ian Fitchet: "Re: 'crafty' took ages to kill"
- Reply: Ian Fitchet: "Re: 'crafty' took ages to kill"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 30 Dec 2003 19:41:16 -0800
On Tue, 30 Dec 2003 19:50:08 +0000 Ian Fitchet <idf@lunanbay.LESS-SPAM.com> wrote:
> see_my_signature_for_my_real_address@hotmail.com (Dr. David Kirkby) writes:
>
>> What can stop a process responding to SIGKILL ??
>
> Nothing can stop it responding to SIGKILL once the signal has been
> delivered. A SIGKILL might well be queued for the process
> (unblockable and unignorable as SIGKILL is) but cannot be delivered
> because, in Solaris: a) the process might be doing IO, b) the process
> might be being traced.
Traced processes ignore SIGKILL? Why can't I trace myself then, to
insist on staying running? I'd be very surprised if this is the case.
/fc
- Next message: uboat2001: "boot cdrom failed - Can't read disk label"
- Previous message: Robb Ottenhoff: "Re: I can not su to root on my Sun Solaris 9 (SPARC) box, even with the correct password"
- In reply to: Ian Fitchet: "Re: 'crafty' took ages to kill"
- Next in thread: Ian Fitchet: "Re: 'crafty' took ages to kill"
- Reply: Ian Fitchet: "Re: 'crafty' took ages to kill"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]