04-06-2011
You have two options
1) Wait for the child.
2) Kill the child, then wait for the child.
Both mean the parent has to know what its children are.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a UNIX daemon process that's been started by a parent process, an application server.
The behavior of this daemon process is to inherit and use the app
server's file descriptors (ports/sockets).
When I shutdown the app server, the daemon continues to run, because there may be other... (1 Reply)
Discussion started by: kunalashar
1 Replies
2. Programming
Hi everybody,
I'm trying to understand how a parent and child processes interact.
This function( below) basically measures the fork time from the perspective of the parent only.
what i would like to know is how to measure the time from the perspective of parent and child (ie: inserting... (0 Replies)
Discussion started by: tosa
0 Replies
3. Shell Programming and Scripting
Hi All,
I have two ksh script. 1st script calls the 2nd script and the second script calls an 'C' program.
I want 1st script to wait until the 'C' program completes.
I cant able to get the process id for the 'C' program (child process) to make the 1st script to wait for the second... (7 Replies)
Discussion started by: sennidurai
7 Replies
4. Solaris
Hi
want to know what file (descriptor+filename+socket) is being accessed by particular process on solaris.
Purpose : while running perf. test, needs to find where is the bottleneck.
We are providing concurrnet load for around 1 hr and needs to capture data related to file usage pattern... (1 Reply)
Discussion started by: raxitsheth
1 Replies
5. Shell Programming and Scripting
Hey all, I need to launch a script from within 2 other scripts that can run independently of the two parent scripts... Im having a hard time doing this, if anyone knows how please let me know.
More detail.
ScriptA (bash), ScriptB (ksh), ScriptC (bash)
ScriptA, launches ScriptB
ScirptB,... (7 Replies)
Discussion started by: trey85stang
7 Replies
6. Shell Programming and Scripting
Hi. !
When I use the 'NOHUP' along with the '&', the process will be running in the background. Even when I attempt to close (Meaning 'EXIT') the session (say PUTTY in this case), it wont exit unless the process is completed.
But, say when I forcefully terminate the session (SHUT DOWN the... (2 Replies)
Discussion started by: WinBarani
2 Replies
7. Emergency UNIX and Linux Support
Hello, everyone.
Here's a program:
pid_t pid = fork();
if (0 == pid) // child process
{
execvp ...;
}
I send a signal (such as SIGINT) to the parent process, the child process receive the signal as well as the parent process.
However I don't want to child process to receive the... (7 Replies)
Discussion started by: jackliang
7 Replies
8. Shell Programming and Scripting
Hi everyone
i am very new to linux , working on bash shell.
I am trying to solve the given problem
1. Create a process and then create children using fork
2. Check the Status of the application for successful running.
3. Kill all the process(threads) except parent and first child... (2 Replies)
Discussion started by: vizz_k
2 Replies
9. UNIX for Advanced & Expert Users
Can any help me in finding the way to close opened file descriptor in Solaris ,without killing process. As accidently a file was removed which was opened by a process.
Much thanks in advance :) (11 Replies)
Discussion started by: nitj
11 Replies
10. Shell Programming and Scripting
Hi all,
I am starting mgen5 for sometime depends on input from a file, in a child process. now I want to make parent to wait in this child process till mgen5 finishes, or timeout happens.
could anyone please tell me how to make parent to wait in child process in shell script?
thanks... (2 Replies)
Discussion started by: girijajoshi
2 Replies
waitid(2) System Calls Manual waitid(2)
NAME
waitid - wait for child process to change state
SYNOPSIS
DESCRIPTION
The function suspends the calling process until one of its children 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 returns immediately.
The idtype and id arguments are used to specify which children will wait for.
If idtype is will wait for the child with a process ID equal to (pid_t)pid.
If idtypeis will wait for any child with a process group ID equal to (pid_t)pid.
If idtypeis will wait for any children and id is ignored.
The options argument is used to specify which state changes will wait for. It is formed by OR-ing together one or more of the following
flags:
Wait for processes that have exited.
Status will be returned for any child that has stopped upon receipt
of a signal.
Status will be returned for any child that was stopped and has been
continued.
Return immediately if there are no children to wait for.
Keep the process whose status is returned in
infop in a waitable state. This will not affect the state of the process; the process may be waited for
again after this call completes.
The infop argument must point to a structure. If 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 will be filled in by the system with the status of the process. The
si_signo member will always be equal to
RETURN VALUE
If returns due to the change of state of one of its children, 0 is returned. Otherwise, -1 is returned and is set to indicate the error.
ERRORS
The function will fail if:
[ECHILD] The calling process has no existing unwaited-for child processes.
[EINTR] The function was interrupted due to the receipt of a signal by the calling process.
[EINVAL] An invalid value was specified for options, or idtype and id specify an invalid set of processes.
APPLICATION USAGE
Threads Considerations
In a multi-threaded application, only the calling thread is suspended by
will not return until all threads in the process have reached the desired state. For example, if the or options are specified, will not
return until all threads in the process have terminated, stopped or continued respectively.
SEE ALSO
exec(2), exit(2), wait(2), <sys/wait.h>.
CHANGE HISTORY
First released in Issue 4, Version 2.
waitid(2)