Sponsored Content
Full Discussion: UNIX signal problem
Top Forums Programming UNIX signal problem Post 302502005 by achenle on Sunday 6th of March 2011 12:41:01 PM
Old 03-06-2011
So, what are the contents of your "struct sigaction sa" when you make the call to sigaction()?
This User Gave Thanks to achenle For This Post:
 

10 More Discussions You Might Find Interesting

1. Programming

[Problem] raise a signal in FreeBSD

I am trying to send a SIGUSR1 to a set of process. Please tell me how to do. I've tried the system call raise(int sig) but it just raise a signal of to the 'current process.' My program is about a network chat server. When a client connects in, The main process will fork a new process... (1 Reply)
Discussion started by: Namely
1 Replies

2. 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

3. 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

4. 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

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. Solaris

Signal Processing in unix

I've read the man page of singal(3) but I still can't quite understand what is the difference between SIGINT, SIGALRM and SIGTERM. Can someone tell me what is the behavioral difference among these 3 signals in kill command? Thanks! (2 Replies)
Discussion started by: joe228
2 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
killpg(2)							System Calls Manual							 killpg(2)

NAME
bsdproc: killpg(), getpgrp(), setpgrp(), signal(), sigvec() - 4.2 BSD-compatible process control facilities SYNOPSIS
Obsolescent Interfaces DESCRIPTION
These calls simulate (and are provided for backward compatibility with) functions of the same name in the 4.2 Berkeley Software Distribu- tion. This version of is equivalent to the system call (see setpgid(2)). This version of is equivalent to the system call (see getpid(2)). is equivalent to the system call (see kill(2)). The function is no longer supported. Please see the manpage for sigaction(2). This version of has the same effect as , where vec->sv_handler is equal to func, vec->sv_mask is equal to 0, and vec->sv_flags is equal to 0. returns the value that would be stored in ovec->sv_handler if the equivalent call would have succeeded. Otherwise, returns -1 and is set to indicate the reason as it would have been set by the equivalent call to For applications that use BSD signal, it is recommended that they use sigaction(2). The system supports an alternative with similar behav- ior to Berkeley Software Distribution, and the API is but its use is not recommended. WARNINGS
While the 4.3 BSD release defined extensions to some of the interfaces described here, only the 4.2 BSD interfaces are emulated by this package. should not be used in conjunction with the facilities described under sigset(3C). Obsolescent Interfaces The function is no longer supported. Please see the manpage for sigaction(2). APPLICATION USAGE
Threads Considerations The signal disposition (such as catch/ignore/default) established by and is shared by all threads in the process. For more information regarding signals and threads, refer to signal(5). AUTHOR
was developed by HP and the University of California, Berkeley. SEE ALSO
ld(1), kill(2), getpid(2), msgop(2), msgsnd(2), msgrcv(2), read(2), semop(2), setpgid(2), setsid(2), wait(2), write(2), sigaction(2) sigset(3C), sigstack(2), bsd_signal(3C), signal(5). killpg(2)
All times are GMT -4. The time now is 07:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy