Sponsored Content
Full Discussion: Process State
Top Forums UNIX for Dummies Questions & Answers Process State Post 302087854 by jim mcnamara on Wednesday 6th of September 2006 10:11:49 AM
Old 09-06-2006
Think of scheduling like this:

There is one copy of the kernel. When a process is the current one, the kernel "attaches" itself (called a context switch) to the process memory. So when the kernel runs a system call on behalf of the process, it is "attached", and runs in the context of the process. It's not two separate entities running.

Process states (in UNIX) are:

R - runnable which means the process has done a context switch and has the kernel.
S - sleeping which means the process is waiting on I/O completion (blocked), a pipe, memory, etc.
T - process has been stopped - sent a SIGSTOP usually with ctrl/z
Z - zombie - a process that has a process image in memory but no context, ie., not swappable.

You can see this in the ps output. If you are not on Linux an have SVR4 flavor of ps,
then you will see another "state"
O - means the process is the one that currenlty has the cpu.

What you ask has to do with system calls like read which block. I don't know what you meant by process state, since I/O blocked=one of the sleep categories
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

child process state

Hi all, I have one requirement,I have two shell programs one is parent and the other one is child . from parent script i need to execute/trigger/call child script as background job. my requirement is after calling child script i want the child process information i.e PID of child weather it is... (8 Replies)
Discussion started by: smreddy
8 Replies

2. Shell Programming and Scripting

Unix script (sh): state of ftp process

Hi guys, I'm writing a script in which I have to get file from a remote host by ftp. The problem is that the remote machine could be very slow, not connected or ok. To resolve this problem, I write this: echo "verbose on" > ftprap.cmd echo "prompt " >> ftprap.cmd echo "ascii"... (3 Replies)
Discussion started by: egiz81
3 Replies

3. UNIX for Advanced & Expert Users

retrieve process state programatically

Assume I spawn a process on (csh) command line, like > du -a / >& /dev/null & which creates a process with id 1234. Now, I can suspend/resume that process with > kill -STOP 1234 > kill -CONT 1234 and can query the process state via 'jobs' or 'ps. How can I though query that state... (6 Replies)
Discussion started by: Andre_Merzky
6 Replies

4. Red Hat

How to Force KILL State -D Process/PID?

Hi Expert, I am not able to kill certain user process as root. I have tried using: pkill -u uname skill KILL -u uname kill -9 PID *** I have not using killall yet, since this server has more than 100 users online atm. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND... (1 Reply)
Discussion started by: regmaster
1 Replies

5. UNIX for Advanced & Expert Users

When a process will go to 'D' state?

I'm using "Linux hostname 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 18:40:08 UTC 2009 i686 GNU/Linux" All the client machines will use Thin-client ,I will use my laptop for working and I will mount my home directory from server to my laptop. If I open the firefox in my laptop the... (1 Reply)
Discussion started by: ungalnanban
1 Replies

6. Shell Programming and Scripting

Script to Kill process which is in hang state

Hi, Can anyone help to create a script that will kill the process which is in hang state. (1 Reply)
Discussion started by: A.Santhosh
1 Replies

7. Shell Programming and Scripting

Problem with a script for checking the state of a process

Hello Everyone, I have a process that should be always running. Unfortunately, this process is getting down almost every 10 minutes. I want to make a script that verify the state of this process: If the process is up, the script shouldn't do nothing and if it's down he should run it. Can... (3 Replies)
Discussion started by: adilyos
3 Replies

8. BSD

Process remians in Running state causing other similar process to sleep and results to system hang

Hi Experts, I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state. On doing cat /proc/<pid>wchan showing the "__init_begin" in the output. Can you please help me here... (0 Replies)
Discussion started by: naveeng
0 Replies

9. UNIX for Advanced & Expert Users

Process remians in Running state causing other similar process to sleep and results to system hang

Hi Experts, I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state. On doing cat /proc/<pid>wchan showing the "__init_begin" in the output. Can you please help me here... (1 Reply)
Discussion started by: naveeng
1 Replies

10. UNIX for Advanced & Expert Users

Process remians in Running state causing other similar process to sleep and results to system hang

Hi Experts, I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state. On doing cat /proc/<pid>wchan showing the "__init_begin" in the output. Can you please help me here... (6 Replies)
Discussion started by: naveeng
6 Replies
RESTART_SYSCALL(2)					     Linux Programmer's Manual						RESTART_SYSCALL(2)

NAME
restart_syscall - restart a system call after interruption by a stop signal SYNOPSIS
int restart_syscall(void); Note: There is no glibc wrapper for this system call; see NOTES. DESCRIPTION
The restart_syscall() system call is used to restart certain system calls after a process that was stopped by a signal (e.g., SIGSTOP or SIGTSTP) is later resumed after receiving a SIGCONT signal. This system call is designed only for internal use by the kernel. restart_syscall() is used for restarting only those system calls that, when restarted, should adjust their time-related parameters--namely poll(2) (since Linux 2.6.24), nanosleep(2) (since Linux 2.6), clock_nanosleep(2) (since Linux 2.6), and futex(2), when employed with the FUTEX_WAIT (since Linux 2.6.22) and FUTEX_WAIT_BITSET (since Linux 2.6.31) operations. restart_syscall() restarts the interrupted system call with a time argument that is suitably adjusted to account for the time that has already elapsed (including the time where the process was stopped by a signal). Without the restart_syscall() mechanism, restarting these system calls would not correctly deduct the already elapsed time when the process continued execution. RETURN VALUE
The return value of restart_syscall() is the return value of whatever system call is being restarted. ERRORS
errno is set as per the errors for whatever system call is being restarted by restart_syscall(). VERSIONS
The restart_syscall() system call is present since Linux 2.6. CONFORMING TO
This system call is Linux-specific. NOTES
There is no glibc wrapper for this system call, because it is intended for use only by the kernel and should never be called by applica- tions. The kernel uses restart_syscall() to ensure that when a system call is restarted after a process has been stopped by a signal and then resumed by SIGCONT, then the time that the process spent in the stopped state is counted against the timeout interval specified in the original system call. In the case of system calls that take a timeout argument and automatically restart after a stop signal plus SIGCONT, but which do not have the restart_syscall(2) mechanism built in, then, after the process resumes execution, the time that the process spent in the stop state is not counted against the timeout value. Notable examples of system calls that suffer this problem are ppoll(2), select(2), and pselect(2). From user space, the operation of restart_syscall() is largely invisible: to the process that made the system call that is restarted, it appears as though that system call executed and returned in the usual fashion. SEE ALSO
sigaction(2), sigreturn(2), signal(7) Linux 2014-12-31 RESTART_SYSCALL(2)
All times are GMT -4. The time now is 06:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy