1 |
On 11/3/06, Alan McKinnon <alan@××××××××××××××××.za> wrote: |
2 |
> On Friday 03 November 2006 06:44, Walter Dnes wrote: |
3 |
> > On Mon, Oct 30, 2006 at 07:48:58PM -0700, Richard Fish wrote |
4 |
> > |
5 |
> > > If -9 doesn't work, it means your kernel is hungup, and yeah, |
6 |
> > > you'll have to reboot to fix. |
7 |
> > |
8 |
> > Where does kill -15 fit in? |
9 |
> |
10 |
> signal 15 is SIGTERM, and the default for kill. The thread is about |
11 |
> unkillable processes, meaning those that don't go away with kill or |
12 |
> kill -15 |
13 |
|
14 |
Just to expand on this a bit... |
15 |
|
16 |
SIGTERM can be caught, blocked, or ignored by a process. It is |
17 |
basically asking the _process_ to "quit now!". |
18 |
|
19 |
SIGKILL cannot be caught, blocked, or ignored by a process. In fact, |
20 |
no user-space code is even executed for SIGKILL. It is basically a |
21 |
request to the kernel to "wipe this thing from memory!". |
22 |
|
23 |
So if SIGKILL doesn't work, that usually means that the process has |
24 |
allocated some resource in the kernel that now cannot be freed. An |
25 |
example would be files open on an NFS server (mounted with the 'hard' |
26 |
option), with dirty buffers needing to be flushed, but the NFS server |
27 |
cannot be reached. SIGKILL would attempt to close those files, which |
28 |
would attempt to flush out those buffers, which would not work. |
29 |
Another example would be a buggy driver and a hung device (seen this |
30 |
with ipw3945d on my own system!) |
31 |
|
32 |
-Richard |
33 |
-- |
34 |
gentoo-user@g.o mailing list |