1 |
* Mick <michaelkintzios@×××××.com> [110723 10:20]: |
2 |
> On Saturday 23 Jul 2011 14:31:23 Todd Goodman wrote: |
3 |
> > * Stroller <stroller@××××××××××××××××××.uk> [110723 09:21]: |
4 |
> > > On 21 July 2011, at 19:48, Dale wrote: |
5 |
> > > > ... |
6 |
> > > > I would try to kill it as root. The -9 option should work. That |
7 |
> > > > hasn't failed me yet. I always run kill commands as root and DOUBLE |
8 |
> > > > check the PID after typing it in. |
9 |
> > > |
10 |
> > > I believe that `kill -9` is bad practice - doesn't it leave memory |
11 |
> > > allocated to the processes as unrecoverable or something? |
12 |
> > > |
13 |
> > > I believe other signals should be attempted first. See the list in `man |
14 |
> > > kill`. I won't swear to it, but `kill -4` sounds right. |
15 |
> > > |
16 |
> > > Stroller. |
17 |
> > |
18 |
> > No, a kill -9 shouldn't leave memory allocated. |
19 |
> > |
20 |
> > However, it is best to try other signals first because it gives the app |
21 |
> > a chance to clean up before closing (if they handle the signals.) But |
22 |
> > that's also why they don't necessarily work. |
23 |
> > |
24 |
> > SIGHUP (kill -1) is the first thing I generally try. Depending on the |
25 |
> > app I may try SIGQUIT (kill -15) but generally it's straight to kill -9 |
26 |
> > if the kill -1 doesn't work. |
27 |
> > |
28 |
> > Todd |
29 |
> |
30 |
> Thanks, I tried kill -15 first and then kill -9. I also tried pkill, killall, |
31 |
> but I got no response from firefox and run out of ideas. |
32 |
> |
33 |
> What does kill -4 do? What is ILL? |
34 |
|
35 |
SIGILL is an illegal instruction. Not one you'd want to use with kill |
36 |
in general. |
37 |
|
38 |
Todd |