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
wait(1) General Commands Manual wait(1)
NAME
wait - await process completion
SYNOPSIS
[pid]
DESCRIPTION
If no argument is specified, waits until all processes (started with of the current shell have completed, and reports on abnormal termina-
tions. If a numeric argument pid is given and is the process ID of a background process, waits until that process has completed. Other-
wise, if pid is not a background process, exits without waiting for any processes to complete.
Because the system call must be executed in the parent process, the shell itself executes without creating a new process (see wait(2)).
Command-Line Arguments
supports the following command line arguments:
The unsigned decimal integer process
ID of a command, whose termination is to wait for.
WARNINGS
Some processes in a 2-or-more-stage pipeline may not be children of the shell, and thus cannot be waited for.
SEE ALSO
csh(1), ksh(1), sh-posix(1), sh(1), wait(2).
STANDARDS CONFORMANCE
wait(1)