News:

Wieners, Brats, Franks, we've got 'em all.

Main Menu

tasklist? taskkill?

Started by rabbit, December 11, 2005, 11:54:40 PM

Previous topic - Next topic

0 Members and 3 Guests are viewing this topic.

rabbit


Sidoh

Quote from: rabbit on December 11, 2005, 11:54:40 PM
Linux equivs?

If you want a full list of processes running:

$ ps -A


If you want to search for a specific process running:

$ ps -aux | grep <proccess_name>


And if you want to kill a process the "unclean" way:

$ killall -9 <process_name>


That's how I know to do it, anyway.  Some of the more linux-literate people may know better ways. :)

Ergot

ps - Lists processes
ps -aux - Lists all processes
kill - Kills process, you need to get the PID from ps.
kill - 9 - If kill fails, this is the "unclean" way like Sidoh said.
top - Lists processes and CPU/Mem usages in realtime

Front-ends(?)
Ksysguard - For KDE
System Monitor - For Gnome
Quote from: Newby on February 26, 2006, 12:16:58 AM
Who gives a damn? I fuck sheep all the time.
Quote from: rabbit on December 11, 2005, 01:05:35 PM
And yes, male both ends.  There are a couple lesbians that need a two-ended dildo...My router just refuses to wear a strap-on.
(05:55:03) JoE ThE oDD: omfg good job i got a boner thinkin bout them chinese bitches
(17:54:15) Sidoh: I love cosmetology

Sidoh

$ ps -aux lists all processes with a bunch of fancy information! :P

$ ps -A is a plain list of processes, but I guess that's not very useful. :)

iago

Quote from: Ergot on December 12, 2005, 12:02:27 AM
ps - Lists processes
ps -aux - Lists all processes
kill - Kills process, you need to get the PID from ps.
kill - 9 - If kill fails, this is the "unclean" way like Sidoh said.
top - Lists processes and CPU/Mem usages in realtime

Front-ends(?)
Ksysguard - For KDE
System Monitor - For Gnome


Beautiful, you stole my answer! :P

rabbit

Well I don't use Gnome so I don't care :P

iago

"top" is probably what you're looking for

Krazed

tasklist = top, or ps -aux (That's what I always did.)

kill PID (Process ID) would end a program while following the program's closing procedure, sends the "SIGTERM" signal.

kill -9 PID would end a program with the "SIGKILL" signal, which instantly kills it, without caring what the program has to say about it or wants to do before closing.
It is good to be good, but it is better to be lucky.

iago

"top" can do all of those, and more.  And is easier to use.  But yes, those are also useful programs :P

Ergot

Wow I never knew top could kill...
Quote from: Newby on February 26, 2006, 12:16:58 AM
Who gives a damn? I fuck sheep all the time.
Quote from: rabbit on December 11, 2005, 01:05:35 PM
And yes, male both ends.  There are a couple lesbians that need a two-ended dildo...My router just refuses to wear a strap-on.
(05:55:03) JoE ThE oDD: omfg good job i got a boner thinkin bout them chinese bitches
(17:54:15) Sidoh: I love cosmetology

Krazed

It is good to be good, but it is better to be lucky.

rabbit

Quote from: Krazed on December 12, 2005, 07:48:50 PM
tasklist = top, or ps -aux (That's what I always did.)

kill PID (Process ID) would end a program while following the program's closing procedure, sends the "SIGTERM" signal.

kill -9 PID would end a program with the "SIGKILL" signal, which instantly kills it, without caring what the program has to say about it or wants to do before closing.
Ah...I remember, I think it was Newby, who said "Windows is like 'please stop running now' but Linux is like 'DIE BITCH!'".  :P

Sidoh

Quote from: rabbit on December 12, 2005, 09:19:53 PM
Ah...I remember, I think it was Newby, who said "Windows is like 'please stop running now' but Linux is like 'DIE BITCH!'".  :P

LMFAO

iago

Quote from: rabbit on December 12, 2005, 09:19:53 PM
Quote from: Krazed on December 12, 2005, 07:48:50 PM
tasklist = top, or ps -aux (That's what I always did.)

kill PID (Process ID) would end a program while following the program's closing procedure, sends the "SIGTERM" signal.

kill -9 PID would end a program with the "SIGKILL" signal, which instantly kills it, without caring what the program has to say about it or wants to do before closing.
Ah...I remember, I think it was Newby, who said "Windows is like 'please stop running now' but Linux is like 'DIE BITCH!'".  :P

Haha, yeah, a non-root process can't catch/discard SIGKILL.  However, a process running as root can, and a process in kernel mode ignores it. 

If you're reading from a harddrive that crashes, so that it gets stuck in an infinite loop in kernel mode, you can't kill it either.