Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: [Problem] raise a signal in FreeBSD
Top Forums Programming [Problem] raise a signal in FreeBSD Post 42984 by Perderabo on Saturday 8th of November 2003 10:11:54 AM
Old 11-08-2003
You need to use kill() rather than raise. Don't let the name of the kill() system call mislead you. kill() sends a signal to a process or a group of processes.

You also want to look at setpgid(). Your main process should call this prior to any forks to create a new process group. Then any child can use kill() to signal the entire process group at once.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

I have a problem using signal SIGUSR2

hi I have created a application which uses SIGUSR2. It send this signal to server and waits for signal SIGUSR2 from server after server performing some operation server sends SIGUSR2 back to the application. The application then quits. This works fine which ran from terminal , but when I... (3 Replies)
Discussion started by: khan_069
3 Replies

2. Programming

Signal Problem

I am using the signal function, and passing it a function named quit procedure...I get the following warning.... passing arg2 of signal from incompatible pointer type... void quit_procedure(void); //this is the way i define my prototype... signal(SIGINT, quit_procedure); Please guide... (5 Replies)
Discussion started by: jacques83
5 Replies

3. Programming

problem with signal()

#include<signal.h> void suicide(); main() { printf("use CTRL \\ for exiting \n"); //signal(SIGINT,SIG_DFL); signal(SIGQUIT,suicide); for (;;); } void suicide() { printf("hello here you r in the suicide code "); } i was just starting with signals .. and tried this ,, but in the... (10 Replies)
Discussion started by: narendra.pant
10 Replies

4. Programming

Problem with signal handler and interrupted system call

Hi, I have a daq program that runs in an infinite loop until it receives SIGINT. A handler catches the signal and sets a flag to stop the while loop. After the loop some things have to be cleaned up. The problem is that I want my main while loop to wait until the next full second begins, to... (2 Replies)
Discussion started by: soeckel
2 Replies

5. Programming

problem in SIGSEGV signal handling

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

6. Programming

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... (2 Replies)
Discussion started by: senvenugopal
2 Replies

7. Programming

UNIX signal problem

Hi all, Sorry about the title,at first i decided to ask a problem about the signal mechanism,however,i'm now figured it out.Sorry to forget modify the title:wall:.I had a small problem that if i use the code which is commented,the code would get a segment fault,while the above code NOT.what's... (4 Replies)
Discussion started by: homeboy
4 Replies

8. Programming

problem in doing coding of signal handler

i m unble to execute code of signal handler using a) Wait b) Waitpid (1 Reply)
Discussion started by: madhura
1 Replies

9. Programming

Losing signal problem

I'm newbie in UNIX programming, I have a problem with signals. I'm writing multithread program, where threads can die at any moment. When thread dies it generates signal SIGUSR1 to main thread and then thread dies. Main thread gets a signal and waits for thread dead. I wrote program like this: ... (5 Replies)
Discussion started by: DendyGamer
5 Replies

10. Linux

Problem with dovecot (Killed with signal 15)

hey, i have been facing a very fatel error with dovecot.. i am getting this error in my dovecot.log file dovecot: Feb 13 15:21:02 Fatal: chdir(/var/mail/folders/user1) failed with uid 1001: Permission denied dovecot: Feb 13 15:21:02 Error: child 18732 (imap) returned error 89 dovecot: Feb... (3 Replies)
Discussion started by: htshshrm2
3 Replies

LEARN ABOUT HPUX

killall

killall(1M)															       killall(1M)

NAME

       killall - kill all active processes

SYNOPSIS

       [signal]

DESCRIPTION

       is a procedure used by to kill all active processes not directly related to the shutdown procedure.

       is chiefly used to terminate all processes with open files so that the mounted file systems are no longer busy and can be unmounted.  sends
       the specified signal to all user processes in the system, with the following exceptions:

	      the process;

	      all processes (including background processes) associated with the terminal from which was invoked;

	      any process, if owned by

	      any process, if owned by

	      any process;

	      any process;

	      any process.

       obtains its process information from and therefore may not be able to perfectly identify which processes to signal (see ps(1)).

       If no signal is specified, a default of (kill) is used.

       is invoked automatically by The use of is recommended over using by itself (see shutdown(1M)).

FILES

SEE ALSO

       fuser(1M), kill(1), ps(1), shutdown(1M), signal(5).

STANDARDS CONFORMANCE

																       killall(1M)
All times are GMT -4. The time now is 11:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy