Re: 'crafty' took ages to kill
From: Ian Fitchet (idf_at_lunanbay.LESS-SPAM.com)
Date: 12/30/03
- Next message: Rich Teer: "Re: a little trouble with "cdrw" and audio disks.."
- Previous message: Barry Margolin: "Re: 'crafty' took ages to kill"
- In reply to: Dr. David Kirkby: "'crafty' took ages to kill"
- Next in thread: Frank Cusack: "Re: 'crafty' took ages to kill"
- Reply: Frank Cusack: "Re: 'crafty' took ages to kill"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 30 Dec 2003 19:50:08 +0000
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.
There are probably other vital and important reasons why the expected
behaviour hasn't happened yet.
And then there are bugs in the OS. Yes, even in Solaris.
Cheers,
Ian
- Next message: Rich Teer: "Re: a little trouble with "cdrw" and audio disks.."
- Previous message: Barry Margolin: "Re: 'crafty' took ages to kill"
- In reply to: Dr. David Kirkby: "'crafty' took ages to kill"
- Next in thread: Frank Cusack: "Re: 'crafty' took ages to kill"
- Reply: Frank Cusack: "Re: 'crafty' took ages to kill"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]