Linux Process: Difference between revisions

From HPCWIKI
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
== Processes states ==
== Processes states ==
  <D Uninterruptible sleep (usually IO)
  S Interruptible sleep (waiting for an event to complete)
D Uninterruptible sleep (usually IO)
  R Running or runnable (on run queue)
  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.
  T Stopped, either by a job control signal or because it is being traced.
  W paging (not valid since the 2.6.xx kernel)
  W paging (not valid since the 2.6.xx kernel)
  X dead (should never be seen)
  X dead (should never be seen)
  Z Defunct ("zombie") process, terminated but not reaped by its parent.</code>
  Z Defunct ("zombie") process, terminated but not reaped by its parent.


  << high-priority (not nice to other users)
  << high-priority (not nice to other users)
Line 13: Line 13:
  s is a session leader
  s is a session leader
  l is multi-threaded (using CLONE_THREAD, like NPTL pthreads do)
  l is multi-threaded (using CLONE_THREAD, like NPTL pthreads do)
  + is in the foreground process group</code>
  + is in the foreground process group
[[File:Linux Process States.png|right|frameless]]
'''You cannot kill "D" state processes, even with [[Linux signal|SIGKILL]] or kill -9'''. As the name implies, they are uninterruptible. You can only clear them by rebooting the server or waiting for the I/O to respond.
 
 
 
 
 
 
 
 
 


== How to know where a process was started and how it was started? ==
== How to know where a process was started and how it was started? ==

Revision as of 08:52, 28 July 2023

Processes states

S Interruptible sleep (waiting for an event to complete)
D Uninterruptible sleep (usually IO)
R Running or runnable (on run queue)
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.
<< 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
Linux Process States.png

You cannot kill "D" state processes, even with SIGKILL or kill -9. As the name implies, they are uninterruptible. You can only clear them by rebooting the server or waiting for the I/O to respond.






How to know where a process was started and how it was started?

Most reliable way is to look at the /proc, /proc/<pid>/ directory where it keeps information like:[1]

  1. cwd link to the current working directory
  2. fd a dir with links to the open files (file descriptors)
  3. cmdline read it to see what command line was used to start the process
  4. environ the environment variables for that process
  5. root a link to what the process considers it's root dir (it will be / unless chrooted)


pstree -sp <PID> also give clearer relationship in tree view


systemctl status <PID>

References