08-10-2009
problem in reforking and signal handling
hi friends i have a problem in signal handling ...
let me explain my problem clearly..
i have four process ..
main process forks two child process and each child process again forks another new process respectively...
the problem is whenever i kill the child process it is reforking and the corresponding its own child process is killed and reforked.. but when i again kill the reforked process of child's new process... it is gettin defunt...
am handling sigchld to kill the child process
is ther any solution for this problem...
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
HI,
I need to handle SIGUSR2 signal in my application to change the state of the application dynamically. I have implemented the signal handler. However the application is able to catch only one SIGUSR2 signal. The second SIGUSR2 signal causes the application to crash. This is happning only with... (3 Replies)
Discussion started by: diganta
3 Replies
2. UNIX for Advanced & Expert Users
Hi
can any please tell me
is it possible to catch the signal in a shell script like we do in C.
if yes please give me some idea or a link. (4 Replies)
Discussion started by: Raom
4 Replies
3. Programming
Hi folks
I'm trying to write a signal handler (in c on HPUX) that will catch the child process launched by execl when it's finished so that I can check a compliance file.
The signal handler appears to catch the child process terminating however when the signal handler completes the parent... (3 Replies)
Discussion started by: themezzaman
3 Replies
4. Shell Programming and Scripting
Guys,
I'm doing signal handling in Perl. I'm trying to catch ^C signal inside the script.
There two scripts : one shell script and one perl script.
The shell script calls the perl script.
For e.g. shell script a.sh and perl scipt sig.pl.
Shell script a.sh looks something like this :... (6 Replies)
Discussion started by: obelix
6 Replies
5. Programming
Hello all,
I am starting to learn signal handling in Linux and have been trying out some simple codes to deal with SIGALRM. The code shown below sets a timer to count down. When the timer is finished a SIGALRM is produced. The handler for the signal just increments a variable called count. This... (7 Replies)
Discussion started by: fox_hound_33
7 Replies
6. Programming
Hi,
I have a main loop which calls a sub loop, which finally returns to the main loop itself. The main loop runs when a flag is set. Now, I have a signal handler for SIGINT, which resets the flag and thus stops the main loop. Suppose I send SIGINT while the program is in subloop, I get an error... (1 Reply)
Discussion started by: Theju
1 Replies
7. Programming
Hi guys,
this is my first posting, so at first hi to everyone! ;)
I have a problem with ucontext_t in connection with signal handling. I want to simulate a preemptive scheduler. I am using the iTimer with ITIMER_PROF, to schedule the interrupts. You find the code below:
#include <stdio.h>... (18 Replies)
Discussion started by: XComp
18 Replies
8. Programming
I am trying to write a small program where I can send signals and then ask for an action to be triggered if that signal is received. For example, here is an example where I am trying to write a programme that will say you pressed ctrl*c when someone presses ctrl+c. My questions are what you would... (1 Reply)
Discussion started by: #moveon
1 Replies
9. Programming
i wrote handler for sigsegv such that i can allocate memory for a variable to which
sigsegv generated for illlegal acces of memory.
my code is
#include <signal.h>
#include<stdio.h>
#include<stdlib.h>
#include<string.h>
char *j;
void segv_handler(int dummy)
{
j=(char *)malloc(10);
... (4 Replies)
Discussion started by: pavan6754
4 Replies
10. UNIX and Linux Applications
Hello,
Can anybody tell me how can i handle segmentation fault signal, in C code? (2 Replies)
Discussion started by: mustus
2 Replies
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 con-
tain 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 sig-
nal.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.10 9 Jun 2004 wait(3C)