Editing Processes in D state
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 16: | Line 16: | ||
First big '''S''' stands for Sleeping, '''R''' stands for running ("+" means that the process is foreground and small "s" means that the process is session leader, but it is not relevant for this article). | First big '''S''' stands for Sleeping, '''R''' stands for running ("+" means that the process is foreground and small "s" means that the process is session leader, but it is not relevant for this article). | ||
| − | '''D''' state occurs then the process is in uninterruptible sleep. This state is bad, because you can't do anything with the process in D state. Fortunately, process normally remains in such state not for so long. But if you have a heap of D state processes then some logic in system is disrupt. If that is happening, the very important thing is to determine where this unlucky sleep occurs. It is easy to do with ps command with ''l'' option. WCHAN column shows the name of the kernel function where the process is sleeping: | + | '''D''' state occurs then the process is in uninterruptible disk sleep. This state is bad, because you can't do anything with the process in D state. Fortunately, process normally remains in such state not for so long. But if you have a heap of D state processes then some logic in system is disrupt. If that is happening, the very important thing is to determine where this unlucky sleep occurs. It is easy to do with ps command with ''l'' option. WCHAN column shows the name of the kernel function where the process is sleeping: |
<pre> | <pre> | ||
