Sponsored Content
Top Forums Programming SIGCHLD interrupts its own handler Post 302404467 by jrichemont on Tuesday 16th of March 2010 02:47:58 PM
Old 03-16-2010
SIGCHLD interrupts its own handler

Hi. I have a program whose job it is to manage 15 child processes. Sometimes these children die (sometimes deliberately other times with a SEGV). This causes a SIGCHLD to be sent to my program which uses waitpid() in the signal handler to gather information and, in most cases, restart the child.
The problem I am having I that under very high loads I am seeing SIGCHLDs sent while the first is still being processed. I can see from my log that the intention was to restart both but only the last one actually gets restarted leading to a gradual haemorrhage of children which eventually causes the whole system to stop responding.

I am using posix threads and have omitted any mutex in the signal handler because I thought it would be atomic. Obviously not. I am a bit scared to put a mutex there; what happens if the same thread is interrupted again while the mutex is held? Deadlock would be worse than the current situation.

I don't want to ignore signals while in the handler either; it is most important that all SIGCHLDs are honoured and the child restarted. I have seen a deferred solution where one thread is dedicated to catching signals and the main program looks at this from time to time. I don't think this will work too well though because I need to call waitpid straight after I get the signal; it needs to wait for the right child status after all.

Any pointers in the right direction would be most welcome.

Cheers;
Jeremy
 

10 More Discussions You Might Find Interesting

1. Programming

Need help with SIGCHLD

Hello everybody, this is my first post on this forum. I have a program that has a child process that sleeps for 5 second and exit. I'm suppose to modify this program so that when the child exits, the parent reports the exit status of the child, so I also have to deal with SIGINT and SIGQUIT. Can... (1 Reply)
Discussion started by: Unlimited Sky
1 Replies

2. UNIX for Advanced & Expert Users

catch SIGCHLD signal in parent process

I want to catch SIGCHLD signal in parent process. I can't use wait() system call to catch SIGCHLD according to project requirment. Operating system linux 3.1 can any one have a solution for this. Thanking you, ranjan (2 Replies)
Discussion started by: ranjan
2 Replies

3. Programming

signal handler for SIGCHLD

Hi, I have an c++ application which uses the function fork and execvp(). The parent does not wait until the child ends. The parents just creates children and let them do their stuff. You can see the parent program as a batch-manager. I have added a SIGCHLD handler to the program: void... (3 Replies)
Discussion started by: jens
3 Replies

4. Programming

When is SIGCHLD is raised.

Hi, I have 2 processes X and Y. Y is exec() from X. In Y i have an exit handler, which is called when i return from main. With in exit handler i delete and object which in turn calls the destructor of the object, which terminates all the threads of Y. I believe that SIGCHLD is raised by Y as... (4 Replies)
Discussion started by: supersumanth
4 Replies

5. Programming

adv reqd on SIGCHLD on accept call

Hi, I have small problem. In my (concurrent)server programm, I am handling accept problem from client like this. sample of server code. /*******************/ end = 0; while (! end ) { sockfd = accept(...) if(sockfd == -1) { if (errno == EINTR) /* this is bcoz... (5 Replies)
Discussion started by: stevenjagan
5 Replies

6. UNIX for Dummies Questions & Answers

About SIGCHLD

When the SIGCHLD is sent? SIGCHLD is sent either a child exits spontaneously (e.g. exit(0)) or it is killed ? thank you in advance (3 Replies)
Discussion started by: Puntino
3 Replies

7. UNIX for Dummies Questions & Answers

Who sent the process SIGCHLD ?

I want to know whicj process send the signal SIGCHLD to the parent's child. Thank you in advance, (1 Reply)
Discussion started by: Puntino
1 Replies

8. Programming

SIGCHLD trace problem

Hello, I'd like to know whether it is possible to let the parent know who kills its child process. The case is likely as below: if there are four processes, we call them A, B, C and D. B is the child of A, and can be killed by both C and D. if B is killed, then A will receive SIGCHLD from B.... (7 Replies)
Discussion started by: aaronwong
7 Replies

9. UNIX for Dummies Questions & Answers

about concept of Interrupts.

Hi all, I am new here ,i want to know about interrupts in detail.What r Interrupts .how they r handeled. Thanx in adavnce. (1 Reply)
Discussion started by: vishwasrao
1 Replies

10. UNIX for Dummies Questions & Answers

using SIGCHLD

I'm testing out how to use SIGCHLD and I had a question about intercepting the signal and executing an action in the signal handler. signal(SIGCHLD,countdown); What I'm trying to achieve is be able to printf(Hello) every second that child is set to sleep. I'm setting sleep = 3; so... (1 Reply)
Discussion started by: l flipboi l
1 Replies
WAIT(2) 						      BSD System Calls Manual							   WAIT(2)

NAME
wait, waitpid, wait4, wait3 -- wait for process termination LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <sys/types.h> #include <sys/wait.h> pid_t wait(int *status); #include <sys/time.h> #include <sys/resource.h> pid_t waitpid(pid_t wpid, int *status, int options); pid_t wait3(int *status, int options, struct rusage *rusage); pid_t wait4(pid_t wpid, int *status, int options, struct rusage *rusage); DESCRIPTION
The wait() function suspends execution of its calling process until status information is available for a terminated child process, or a sig- nal is received. On return from a successful wait() call, the status area contains termination information about the process that exited as defined below. The wait4() system call provides a more general interface for programs that need to wait for certain child processes, that need resource uti- lization statistics accumulated by child processes, or that require options. The other wait functions are implemented using wait4(). The wpid argument specifies the set of child processes for which to wait. If wpid is -1, the call waits for any child process. If wpid is 0, the call waits for any child process in the process group of the caller. If wpid is greater than zero, the call waits for the process with process id wpid. If wpid is less than -1, the call waits for any process whose process group id equals the absolute value of wpid. The status argument is defined below. The options argument contains the bitwise OR of any of the following options. The WCONTINUED option indicates that children of the current process that have continued from a job control stop, by receiving a SIGCONT signal, should also have their status reported. The WNOHANG option is used to indicate that the call should not block if there are no processes that wish to report status. If the WUNTRACED option is set, children of the current process that are stopped due to a SIGTTIN, SIGTTOU, SIGTSTP, or SIGSTOP signal also have their status reported. The WSTOPPED option is an alias for WUNTRACED. The WNOWAIT option keeps the process whose status is returned in a waitable state. The process may be waited for again after this call completes. If rusage is non-zero, a summary of the resources used by the terminated process and all its children is returned (this information is cur- rently not available for stopped or continued processes). When the WNOHANG option is specified and no processes wish to report status, wait4() returns a process id of 0. The waitpid() function is identical to wait4() with an rusage value of zero. The older wait3() call is the same as wait4() with a wpid value of -1. The following macros may be used to test the manner of exit of the process. One of the first three macros will evaluate to a non-zero (true) value: WIFCONTINUED(status) True if the process has not terminated, and has continued after a job control stop. This macro can be true only if the wait call specified the WCONTINUED option). WIFEXITED(status) True if the process terminated normally by a call to _exit(2) or exit(3). WIFSIGNALED(status) True if the process terminated due to receipt of a signal. WIFSTOPPED(status) True if the process has not terminated, but has stopped and can be restarted. This macro can be true only if the wait call specified the WUNTRACED option or if the child process is being traced (see ptrace(2)). Depending on the values of those macros, the following macros produce the remaining status information about the child process: WEXITSTATUS(status) If WIFEXITED(status) is true, evaluates to the low-order 8 bits of the argument passed to _exit(2) or exit(3) by the child. WTERMSIG(status) If WIFSIGNALED(status) is true, evaluates to the number of the signal that caused the termination of the process. WCOREDUMP(status) If WIFSIGNALED(status) is true, evaluates as true if the termination of the process was accompanied by the creation of a core file containing an image of the process when the signal was received. WSTOPSIG(status) If WIFSTOPPED(status) is true, evaluates to the number of the signal that caused the process to stop. NOTES
See sigaction(2) for a list of termination signals. A status of 0 indicates normal termination. If a parent process terminates without waiting for all of its child processes to terminate, the remaining child processes are assigned the parent process 1 ID (the init process ID). If a signal is caught while any of the wait() calls are pending, the call may be interrupted or restarted when the signal-catching routine returns, depending on the options in effect for the signal; see discussion of SA_RESTART in sigaction(2). The implementation queues one SIGCHLD signal for each child process whose status has changed, if wait() returns because the status of a child process is available, the pending SIGCHLD signal associated with the process ID of the child process will be discarded. Any other pending SIGCHLD signals remain pending. If SIGCHLD is blocked, wait() returns because the status of a child process is available, the pending SIGCHLD signal will be cleared unless another status of the child process is available. RETURN VALUES
If wait() returns due to a stopped, continued, or terminated child process, the process ID of the child is returned to the calling process. Otherwise, a value of -1 is returned and errno is set to indicate the error. If wait4(), wait3(), or waitpid() returns due to a stopped, continued, or terminated child process, the process ID of the child is returned to the calling process. If there are no children not previously awaited, -1 is returned with errno set to ECHILD. Otherwise, if WNOHANG is specified and there are no stopped, continued or exited children, 0 is returned. If an error is detected or a caught signal aborts the call, a value of -1 is returned and errno is set to indicate the error. ERRORS
The wait() function will fail and return immediately if: [ECHILD] The calling process has no existing unwaited-for child processes. [ECHILD] No status from the terminated child process is available because the calling process has asked the system to discard such status by ignoring the signal SIGCHLD or setting the flag SA_NOCLDWAIT for that signal. [EFAULT] The status or rusage argument points to an illegal address. (May not be detected before exit of a child process.) [EINTR] The call was interrupted by a caught signal, or the signal did not have the SA_RESTART flag set. SEE ALSO
_exit(2), ptrace(2), sigaction(2), exit(3), siginfo(3) STANDARDS
The wait() and waitpid() functions are defined by POSIX; wait4() and wait3() are not specified by POSIX. The WCOREDUMP() macro and the abil- ity to restart a pending wait() call are extensions to the POSIX interface. HISTORY
The wait() function appeared in Version 6 AT&T UNIX. BSD
November 12, 2005 BSD
All times are GMT -4. The time now is 10:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy