top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

In the ps results few of the processes are having process state as "D" . What does it mean ?

+2 votes
315 views

In the ps results few of the processes are having process state as "D" . What does it mean ? Briefly explain different process states ?

posted Sep 29, 2015 by Mohammed Hussain

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

To have a dynamic view of a process in Linux, always use the top command. This command provides a real-time view of the Linux system in terms of processes. The eighth column in the output of this command represents the current state of processes. A process state gives a broader indication of whether the process is currently running, stopped, sleeping etc.

A process in Linux can have any of the following four states…

Running – A process is said to be in a running state when either it is actually running/ executing or waiting in the scheduler’s queue to get executed (which means that it is ready to run). That is the reason that this state is sometimes also known as ‘runnable’ and represented by (R).

Waiting or Sleeping – A process is said to be in this state if it is waiting for an event to occur or waiting for some resource-specific operation to complete. So, depending upon these scenarios, a waiting state can be subcategorised into an interruptible (S) or uninterruptible (D) state respectively.

Stopped – A process is said to be in the stopped state when it receives a signal to stop. This usually happens when the process is being debugged. This state is represented by (T).

Zombie – A process is said to be in the zombie state when it has finished execution but is waiting for its parent to retrieve its exit status. This state is represented by (Z).

Apart from these four states, the process is said to be dead after it crosses over the zombie state; ie when the parent retrieves its exit status. ‘Dead’ is not exactly a state, since a dead process ceases to exist.

answer Sep 30, 2015 by Manikandan J
Similar Questions
+6 votes

Is there any way to kill the process which went to uninterruptible sleep (D) state due of some reason without rebooting machine??

I observed one of the process went to D-state during performance runs. Now, not able to kill the process using pkill or kill commands? Finally, we have to reboot the Linux machine.

Can anyone helps me out for this situation?? I don't want to reboot the machine.

We can kill the Zombie (Z) process but not able to kill process which is in D-state.

+4 votes

So many times, we make foreground process to background process in linux system. How does it handle internally ?

+1 vote

As far as i know when a process is created, 8MB of stack is allocated to it.
Is it right?

If not then is there any fix size or not?

If yes then please answer and Help To solve this question also.

+1 vote

I have few questions about Cache Memory

In my system "free -h" command gave me below output,

      total        used        free      shared  buff/cache   available
Mem:   7.6G        2.1G        1.5G         46M        4.0G        4.8G
Swap:  1.6G         28M        1.6G

1. Why "Cache Memory" is required inside the main memory?

As far as i know "Cache Memory" is different than the main memory(RAM), It is very costly and it is very faster, Please Correct me if i am wrong.

2. Before 1 hour this cache memory was 3 GB and then it is increased by 1 GB?

Please note that I din't start/run any new processes

3. Till what limit i can start new processes/application?

I mean as per free -h command output,

free memory = 1.5 GB, Cache memory = 4 GB and Swap memory = 1.6 GB

can i start new application up to (1.5 + 1.6) GB or (1.5 + 1.6 + 4) GB`?

4. Can i set/configure this cache memory value?

If yes, then how to?

+2 votes

Which option is used in "ps" command to get the details on running threads associated to a process ?

...