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)
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)
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)
#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)
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)
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)
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)
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)
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 LINUX
bsd_signal
BSD_SIGNAL(3) Linux Programmer's Manual BSD_SIGNAL(3)NAME
bsd_signal - signal handling with BSD semantics
SYNOPSIS
#define _XOPEN_SOURCE
#include <signal.h>
typedef void (*sighandler_t)(int);
sighandler_t bsd_signal(int signum, sighandler_t handler);
DESCRIPTION
The bsd_signal() function takes the same arguments, and performs the same task, as signal(2).
The difference between the two is that bsd_signal() is guaranteed to provide reliable signal semantics, that is: a) the disposition of the
signal is not reset to the default when the handler is invoked; b) delivery of further instances of the signal is blocked while the signal
handler is executing; and c) if the handler interrupts a blocking system call, then the system call is automatically restarted. A portable
application cannot rely on signal(2) to provide these guarantees.
RETURN VALUE
The bsd_signal() function returns the previous value of the signal handler, or SIG_ERR on error.
ERRORS
As for signal(2).
CONFORMING TO
4.2BSD, POSIX.1-2001. POSIX.1-2008 removes the specification of bsd_signal(), recommending the use of sigaction(2) instead.
NOTES
Use of bsd_signal() should be avoided; use sigaction(2) instead.
On modern Linux systems, bsd_signal() and signal(2) are equivalent. But on older systems, signal(2) provided unreliable signal semantics;
see signal(2) for details.
The use of sighandler_t is a GNU extension; this type is only defined if the _GNU_SOURCE feature test macro is defined.
SEE ALSO sigaction(2), signal(2), sysv_signal(3), feature_test_macros(7), signal(7)COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
2009-03-15 BSD_SIGNAL(3)