.\" Added section on stop/cont signals interrupting syscalls.
.\" 2008-10-05, mtk: various additions
.\"
-.TH SIGNAL 7 2010-09-19 "Linux" "Linux Programmer's Manual"
+.TH SIGNAL 7 2011-09-18 "Linux" "Linux Programmer's Manual"
.SH NAME
signal \- overview of signals
.SH DESCRIPTION
(This is the system call used to implement
.BR pthread_kill (3).)
.TP
-.BR sigqueue (2)
+.BR sigqueue (3)
Sends a real-time signal with accompanying data to a specified process.
.SS Waiting for a Signal to be Caught
The following system calls suspend execution of the calling process
Unlike standard signals, real-time signals have no predefined meanings:
the entire set of real-time signals can be used for application-defined
purposes.
-(Note, however, that the LinuxThreads implementation uses the first
-three real-time signals.)
.PP
The default action for an unhandled real-time signal is to terminate the
receiving process.
while that signal is currently blocked, then only one instance is queued.
.IP 2. 4
If the signal is sent using
-.BR sigqueue (2),
+.BR sigqueue (3),
an accompanying value (either an integer or a pointer) can be sent
with the signal.
If the receiving process establishes a handler for this signal using the
.BR getrlimit (2),
.BR kill (2),
.BR killpg (2),
+.BR rt_sigqueueinfo (2),
.BR setitimer (2),
.BR setrlimit (2),
.BR sgetmask (2),
.BR signalfd (2),
.BR sigpending (2),
.BR sigprocmask (2),
-.BR sigqueue (2),
.BR sigsuspend (2),
.BR sigwaitinfo (2),
.BR abort (3),
.BR longjmp (3),
.BR raise (3),
.BR pthread_sigqueue (3),
+.BR sigqueue (3),
.BR sigset (3),
.BR sigsetops (3),
.BR sigvec (3),