Originally Posted by ethics
ps aux | grep <process>
That'll give you useful output on a particular process then you can kill it with
kill <process_ID (pid)>p
If you're using a regex in the grep to find a particular process or set of processes, you may as well use pkill
. It basically takes the manual intervention out of copying and pasting the process number, so instead of 'ps aux | grep foo' -> 'kill <foo's PID>', you can just type pkill foo
. Unlike the grepping though, it only searches the process name, so anchors like ^ work nicely.
I'm not sure if it's as universal as grep, but IIRC it's been on most every system I've used.
Oh, and in one of the window managers, Ctrl-Shift-Esc brings up a graphical task manager, like in Windows. I forget which though (not Fluxbox
)... anyone able to confirm?
Originally Posted by rlnd
...now I cannot find the meanings in the field "STAT" .........how is when a task is "hanged" ?
From man ps
PROCESS STATE CODES
Here are the different values that the s, stat and state output specifiers
(header "STAT" or "S") will display to describe the state of a process.
D Uninterruptible sleep (usually IO)
R Running or runnable (on run queue)
S Interruptible sleep (waiting for an event to complete)
T Stopped, either by a job control signal or because it is being traced.
W paging (not valid since the 2.6.xx kernel)
X dead (should never be seen)
Z Defunct ("zombie") process, terminated but not reaped by its parent.
For BSD formats and when the stat keyword is used, additional characters may
< high-priority (not nice to other users)
N low-priority (nice to other users)
L has pages locked into memory (for real-time and custom IO)
s is a session leader
l is multi-threaded (using CLONE_THREAD, like NPTL pthreads do)
+ is in the foreground process group
Of course, the actual answer to your question depends on what you mean by "hanged".