04-26-2008
Sure. The reasoning of it is the entire design architecture
behind a session and process group. If you are not familiar with
these unix concepts programatically W.Richard Stevens
is an invaluable resource.
It sounds like you may be coming from a windows environment.
As Perderabo notes the ability for a process to wait
on another processes session or process group introduces
ineradicable security issues for unix and unix-alikes.
A threaded model is more easily adapted because of
shared address space.
My advice is to use threads if you are uncomfortable with the process paradigm.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
is-it normal to have 86% of CPU for wait commande :
ps aux| head -20
UTIL PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 516 86,6 0,0 12 12 - A 02 nov 2088:03 wait
oralfa01 54422 4,6 1,0 68044 39868 - A 09:20:06 2:27 oracleALFA01
If... (3 Replies)
Discussion started by: big123456
3 Replies
2. UNIX for Dummies Questions & Answers
When running top, I notice a bit more I/O wait time than usual. Is there a tool or piece of software out there that can me help evaluate the performance of these operations on my machine? Thanks! (5 Replies)
Discussion started by: unavb
5 Replies
3. Shell Programming and Scripting
:cool:
I need to execute a shell script to do the following:
cat a file
run two back ground processes using the first two values from the file
wait till those background processes finish
run two more background processes using the next two values from the file
wait till those background... (1 Reply)
Discussion started by: halo98
1 Replies
4. Shell Programming and Scripting
In one of the shell script (Where abinitio graph is called), the last line is wait ${!}. What does this wait ${!} mean ??? (2 Replies)
Discussion started by: risshanth
2 Replies
5. Shell Programming and Scripting
Did not use 'wait' yet.
How I understand by now the wait works only for child processes, started background.
Is there any other way to watch completion of any, not related process (at least, a process, owned by the same user?)
I need to start a background process, witch will be waiting... (2 Replies)
Discussion started by: alex_5161
2 Replies
6. UNIX for Advanced & Expert Users
can any one please give me clear idea of wait process in UNIX system.
I am using AIX 5.3 and see loots of wait process. I have very basic concept of wait process. If CPU has nothing to do then a wait process is generated per CPU. But i want know the detail how is it forked.
Is wait a jombe... (2 Replies)
Discussion started by: pchangba1
2 Replies
7. Red Hat
Can someone explain what is the status says WAIT on performance monitoring
command.. (2 Replies)
Discussion started by: suresh_krish
2 Replies
8. Shell Programming and Scripting
Hi Gurus,
Some questions regarding wait. I have tried searching in this forum for threads on wait but not completely got what I am looking for.
Background:
One script (.sh) that starts/calls a reference to an application's executable and submits a batch job to it. Objective is to wait... (2 Replies)
Discussion started by: rsheikh
2 Replies
9. Shell Programming and Scripting
Hi,
I am facing a strange issue,
when i call a script from my while loop in background it doesnt go in background, despite the wait i put below the whil loop it goes forward even before the process put in background is completed.
cat abc.txt | while read -u4 line
do
#if line contains #... (2 Replies)
Discussion started by: mihirvora16
2 Replies
10. Shell Programming and Scripting
Hi,
written a script which uses wait as follows
Main.sh
#!/usr/bin/ksh
nohup scrpit1 1 &
pid_1=$!
nohup scrpit1 2 &
pid_2=$!
wait $pid_1
wait $pid_2
nohup scrpit1 3 &
pid_1=$!
nohup scrpit1 4 & (1 Reply)
Discussion started by: krux_rap
1 Replies
WAITID(P) POSIX Programmer's Manual WAITID(P)
NAME
waitid - wait for a child process to change state
SYNOPSIS
#include <sys/wait.h>
int waitid(idtype_t idtype, id_t id, siginfo_t *infop, int options);
DESCRIPTION
The waitid() function shall suspend the calling thread until one child of the process containing the calling thread changes state. It
records the current state of a child in the structure pointed to by infop. If a child process changed state prior to the call to waitid(),
waitid() shall return immediately. If more than one thread is suspended in wait() or waitpid() waiting for termination of the same process,
exactly one thread shall return the process status at the time of the target process termination.
The idtype and id arguments are used to specify which children waitid() waits for.
If idtype is P_PID, waitid() shall wait for the child with a process ID equal to (pid_t)id.
If idtype is P_PGID, waitid() shall wait for any child with a process group ID equal to (pid_t)id.
If idtype is P_ALL, waitid() shall wait for any children and id is ignored.
The options argument is used to specify which state changes waitid() shall wait for. It is formed by OR'ing together one or more of the
following flags:
WEXITED
Wait for processes that have exited.
WSTOPPED
Status shall be returned for any child that has stopped upon receipt of a signal.
WCONTINUED
Status shall be returned for any child that was stopped and has been continued.
WNOHANG
Return immediately if there are no children to wait for.
WNOWAIT
Keep the process whose status is returned in infop in a waitable state. This shall not affect the state of the process; the process
may be waited for again after this call completes.
The application shall ensure that the infop argument points to a siginfo_t structure. If waitid() returns because a child process was found
that satisfied the conditions indicated by the arguments idtype and options, then the structure pointed to by infop shall be filled in by
the system with the status of the process. The si_signo member shall always be equal to SIGCHLD.
RETURN VALUE
If WNOHANG was specified and there are no children to wait for, 0 shall be returned. If waitid() returns due to the change of state of one
of its children, 0 shall be returned. Otherwise, -1 shall be returned and errno set to indicate the error.
ERRORS
The waitid() function shall fail if:
ECHILD The calling process has no existing unwaited-for child processes.
EINTR The waitid() function was interrupted by a signal.
EINVAL An invalid value was specified for options, or idtype and id specify an invalid set of processes.
The following sections are informative.
EXAMPLES
None.
APPLICATION USAGE
None.
RATIONALE
None.
FUTURE DIRECTIONS
None.
SEE ALSO
exec() , exit() , wait() , the Base Definitions volume of IEEE Std 1003.1-2001, <sys/wait.h>
COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol-
ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of
Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE
and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained
online at http://www.opengroup.org/unix/online.html .
IEEE
/The Open Group 2003 WAITID(P)