08-07-2009
#matrixmadhan
Sorry for late reply.
Actually i was implementing the above program so i was bit busy, still i m facing one problem as i said earlier, how do i know which child sent me a signal, its not SIGCHLD , i m sending user defined signal to parent, and in sig handler i m not able to know which child sent me a signal, my child is running forever, means once the particular child sent me a singnal i wiil reasign some task to it, but i m not able to identify.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am running HP-UX B.11.11.
I'm increasing a parameter for a database engine so that it uses more memory to buffer the disk drive (to speed up performance). I have over 5GB of memory not being used.
But when I try to start the DB with the increased buffer parameter I get told.
"Not... (1 Reply)
Discussion started by: cjcamaro
1 Replies
2. Programming
Between mmap and shared memory which is the best method of sharing data between multiple applications, interms of speed? (1 Reply)
Discussion started by: nmds
1 Replies
3. Programming
Today, I wrote a test code for fork/execvp/waitpid. In the parent process, it fork 100 child processes which only execute "date" to print the current datetime. When any child process die, the parent process will receive a SIGCHLD signal. Then, the parent process will re-fork-execvp the child... (7 Replies)
Discussion started by: whererush
7 Replies
4. Programming
hi,
this is the problem: i want to swap a linked list between 4 processes (unrelated), is there any way i can do that just by sending a pointer to a structure?
//example
typedef struct node
{
int x;
char c;
struct node *next;
} node;
or i should send the items ( x,c ) by... (9 Replies)
Discussion started by: elzalem
9 Replies
5. Programming
I need to create a shared library to access an in memory DB. The DB is not huge, but big enough to make it cumbersome to carry around in every single process using the shared library. Luckily, it is pretty static information, so I don't need to worry much about synchronizing the data between... (12 Replies)
Discussion started by: DreamWarrior
12 Replies
6. Programming
I am writing a shared library in Linux (but compatible with other UNIXes) and I want to allow multiple instances to share a piece of memory -- 1 byte is enough. What's the "best" way to do this? I want to optimize for speed and portability.
Obviously, I'll have to worry about mutual exclusion. (0 Replies)
Discussion started by: otheus
0 Replies
7. Programming
hi, i want to write a code for forking 3 4 child. n wants that every child process one of the account from global account list. i wrote a program for that, but problem is every child is processing every account in list. what can me done to avoid it.
attaching code with it
#include <stdio.h>... (2 Replies)
Discussion started by: anup13
2 Replies
8. Programming
Hi gurus, I would like to fork more children and then write their return values: so far I tried:
#include <stdio.h>
#include <stdlib.h>
#include <errno.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/wait.h>
int main(void)
{
pid_t pid;
int rv=0, i;
... (5 Replies)
Discussion started by: wakatana
5 Replies
9. Programming
hello everyone,
i am making a tcp chat server using c in linux. i have used socket programming to connect the server and the client.
can anyone please let me know how i can use forking for multiple clients??
thank you (1 Reply)
Discussion started by: sweetbella
1 Replies
10. Programming
Hello.
I am new to this forum and I would like to ask for advice about low level POSIX programming.
I have to implement a POSIX compliant C shared library.
A file will have some variables and the shared library will have some functions which need those variables.
There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies
LEARN ABOUT OPENSOLARIS
wait
wait(3C) Standard C Library Functions wait(3C)
NAME
wait - wait for child process to stop or terminate
SYNOPSIS
#include <sys/types.h>
#include <sys/wait.h>
pid_t wait(int *stat_loc);
DESCRIPTION
The wait() function will suspend execution of the calling thread until status information for one of its terminated child processes is
available, or until delivery of a signal whose action is either to execute a signal-catching function or to terminate the process. If more
than one thread is suspended in wait(), waitpid(3C), or waitid(2) awaiting termination of the same process, exactly one thread will return
the process status at the time of the target process termination. If status information is available prior to the call to wait(), return
will be immediate.
If wait() returns because the status of a child process is available, it returns the process ID of the child process. If the calling
process specified a non-zero value for stat_loc, the status of the child process is stored in the location pointed to by stat_loc. That
status can be evaluated with the macros described on the wait.h(3HEAD) manual page.
In the following, status is the object pointed to by stat_loc:
o If the child process terminated due to an _exit() call, the low order 8 bits of status will be 0 and the high order 8 bits will
contain the low order 7 bits of the argument that the child process passed to _exit(); see exit(2).
o If the child process terminated due to a signal, the high order 8 bits of status will be 0 and the low order 7bits will contain
the number of the signal that caused the termination. In addition, if WCOREFLG is set, a "core image" will have been produced;
see signal.h(3HEAD) and wait.h(3HEAD).
One instance of a SIGCHLD signal is queued for each child process whose status has changed. If wait() returns because the status of a child
process is available, any pending SIGCHLD signal associated with the process ID of that child process is discarded. Any other pending
SIGCHLD signals remain pending.
If the calling process has SA_NOCLDWAIT set or has SIGCHLD set to SIG_IGN, and the process has no unwaited children that were transformed
into zombie processes, it will block until all of its children terminate, and wait() will fail and set errno to ECHILD.
If a parent process terminates without waiting for its child processes to terminate, the parent process ID of each child process is set to
1, with the initialization process inheriting the child processes; see Intro(2).
RETURN VALUES
When wait() returns due to a terminated child process, the process ID of the child is returned to the calling process. Otherwise, -1 is
returned and errno is set to indicate the error.
ERRORS
The wait() function will fail if:
ECHILD The calling process has no existing unwaited-for child processes.
EINTR The function was interrupted by a signal.
USAGE
Since wait() blocks on a stopped child, a calling process wanting to see the return results of such a call should use waitpid(3C) or
waitid(2) instead of wait(). The wait() function is implemented as a call to waitpid(-1, stat_loc, 0).
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
|MT-Level |Async-Signal-Safe |
+-----------------------------+-----------------------------+
SEE ALSO
Intro(2), exec(2), exit(2), fork(2), pause(2), waitid(2), ptrace(3C), signal(3C), signal.h(3HEAD), waitpid(3C), wait.h(3HEAD),
attributes(5)
SunOS 5.11 9 Jun 2004 wait(3C)