Click to See Complete Forum and Search --> : Killing processes...


Wallex
08-25-2002, 10:44 PM
I did it again... I played too much with the Gimp and I broke it. I had to kill the client, but whenever I do that to the Gimp, it seems 'somehow' the Gimp is still alive and sucking my cpu. Gkrell Monitor shows 100% cpu usage all the time, and the only way to stop it is by killing the loose thread. On KDE I would just open the ksysguard and kill the process with the highest cpu%, but here in Fluxbox Ksysguard doesn't 'works' (it can't track the processes, I guess), and well.. how can I do that? I need to find out the pid of the process that's eating my resources so I can kill it... and since I didn't start the Gimp from the console, I can't just use jobs or something like that to track it... can I?

Bokkenka
08-25-2002, 11:02 PM
Open a terminal and use the command "top" . It will list out the processes, and give several columns of info... pid, user, size, %cpu, %mem, and command-name. Then hit "P", that's a capital P, and it will sort them by processor-usage. You can then use "k", lower-case, to kill the process you want. While it top, hit "h" for the help sheet.

Wallex
08-25-2002, 11:07 PM
Hey thanks! Top, eh? I think I'll add that to my menu. Nice to receive help about killing from an assassin... sounds fitting if you ask me.

KageMurai
08-26-2002, 04:45 AM
You can use

ps ax

to list all the running processes. Afterwards you can either

kill process-id

or

killall processname

but take care and don't kill too much :D