12-02-2011
Is fprintf() listed as an async-signal safe call?
10 More Discussions You Might Find Interesting
1. Programming
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
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
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
#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
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
6. 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
7. Programming
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
8. Programming
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
9. Programming
i m unble to execute code of
signal handler using
a) Wait b) Waitpid (1 Reply)
Discussion started by: madhura
1 Replies
10. Linux
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
sigpause
sigpause(3C) sigpause(3C)
NAME
sigpause - signal management
SYNOPSIS
Obsolescent
DESCRIPTION
The function, along with the and functions provide simplified signal management.
The function removes sig from the calling thread's signal mask and suspends the calling thread until a signal is received. The function
restores the thread's signal mask to its original state before returning.
RETURN VALUE
The function suspends execution of the thread until a signal is received, whereupon it shall return and set to
ERRORS
[EINVAL] sig is not a valid signal number.
WARNINGS
The compiler option must be set to use sigpause(). The use of the function without the option is unspecified.
should not be used in conjunction with signal(2) and sigspace(2).
OBSOLESCENT FUNCTION
will be obsoleted in the near future. The obsolescent function blocks signals according to the value of mask, then atomically waits for an
unmasked signal to arrive. On return, restores the current signal mask to the value that existed before the call. When no signals are to
be blocked, a value of is used for mask.
terminates when it is interrupted by a signal. When terminates, it returns -l and sets to
The obsolescent function is typically used in conjunction with the obsoleted function.
Threads Considerations
Since blocked signal masks are maintained at the thread level, the obsolescent function modifies only the calling thread's blocked signal
mask. suspends only the calling thread until it receives a signal.
If other threads in the process do not block the signal, the signal may be delivered to another thread in the process and the thread in may
continue waiting. For this reason, the use of sigwait(2) is recommended instead of for multi-threaded applications.
For more information regarding signals and threads, refer to signal(5).
LP64 Programs
This obsolescent accepts a long (64 bit) value. However, as for ILP32 programs, supports signals numbered 1 through 32. The upper 32 bits
of the mask argument are ignored.
Author
was developed by the University of California, Berkeley.
SEE ALSO
kill(1), kill(2), pause(2), signal(2), wait(2), abort(3C), setjmp(3C), sighold(3C), sigignore(3C), sigrelse(3C), sigset(3C), signal(5).
STANDARDS CONFORMANCE
sigpause(3C)