getrlimit.2, kill.2, rt_sigqueueinfo.2, sigaction.2, signal.2, signalfd.2, sigprocmask.2, sigwaitinfo.2, psignal.3, pthread_sigqueue.3, credentials.7, signal.7: Change reference to "sigqueue(2)" to "sigqueue(3)"

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2011-09-18 06:27:57 +02:00
parent 7767750f4b
commit 485ab7013e
12 changed files with 26 additions and 27 deletions

View File

@ -352,7 +352,7 @@ that may be queued for the real user ID of the calling process.
Both standard and real-time signals are counted for the purpose of
checking this limit.
However, the limit is only enforced for
.BR sigqueue (2);
.BR sigqueue (3);
it is always possible to use
.BR kill (2)
to queue one instance of any of the signals that are not already
@ -628,8 +628,8 @@ was greater than
.BR quotactl (2),
.BR sbrk (2),
.BR shmctl (2),
.BR sigqueue (2),
.BR malloc (3),
.BR sigqueue (3),
.BR ulimit (3),
.BR core (5),
.BR capabilities (7),

View File

@ -171,9 +171,9 @@ to all of the processes for which the caller had permission to signal.
.BR _exit (2),
.BR killpg (2),
.BR signal (2),
.BR sigqueue (2),
.BR tkill (2),
.BR exit (3),
.BR sigqueue (3),
.BR capabilities (7),
.BR credentials (7),
.BR signal (7)

View File

@ -45,8 +45,7 @@ flag.
These system calls are not intended for direct application use;
they are provided to allow the implementation of
.BR sigqueue (2)
.\" FIXME sigqueue is actually a library function
.BR sigqueue (3)
and
.BR pthread_sigqueue (3).
@ -102,7 +101,7 @@ This field contains the user data to accompany the signal.
For more information, see the description of the last
.RI ( "union sigval" )
argument of
.BR sigqueue (2).
.BR sigqueue (3).
.PP
Internally, the kernel sets the
.I si_signo
@ -185,7 +184,7 @@ or thread exists.
.BR kill (2),
.BR sigaction (2),
.BR sigprocmask (2),
.BR sigqueue (2),
.BR tgkill (2),
.BR pthread_sigqueue (3),
.BR sigqueue (3),
.BR signal (7)

View File

@ -295,16 +295,16 @@ read the fields that are meaningful for the given signal:
Signals sent with
.BR kill (2)
and
.BR sigqueue (2)
.BR sigqueue (3)
fill in
.IR si_pid " and " si_uid .
In addition, signals sent with
.BR sigqueue (2)
.BR sigqueue (3)
fill in
.IR si_int " and " si_ptr
with the values specified by the sender of the signal;
see
.BR sigqueue (2)
.BR sigqueue (3)
for more details.
.IP *
Signals sent by POSIX.1b timers (since Linux 2.6) fill in
@ -451,7 +451,7 @@ or
Sent by the kernel.
.TP
.B SI_QUEUE
.BR sigqueue (2)
.BR sigqueue (3)
.TP
.B SI_TIMER
POSIX timer expired
@ -789,11 +789,11 @@ See
.BR signalfd (2),
.BR sigpending (2),
.BR sigprocmask (2),
.BR sigqueue (2),
.BR sigsuspend (2),
.BR wait (2),
.BR raise (3),
.BR siginterrupt (3),
.BR sigqueue (3),
.BR sigsetops (3),
.BR sigvec (3),
.BR core (5),

View File

@ -266,11 +266,11 @@ provides BSD semantics.
.BR signalfd (2),
.BR sigpending (2),
.BR sigprocmask (2),
.BR sigqueue (2),
.BR sigsuspend (2),
.BR bsd_signal (3),
.BR raise (3),
.BR siginterrupt (3),
.BR sigqueue (3),
.BR sigsetops (3),
.BR sigvec (3),
.BR sysv_signal (3),

View File

@ -183,8 +183,8 @@ struct signalfd_siginfo {
uint32_t ssi_trapno; /* Trap number that caused signal */
.\" ssi_trapno is unused on most arches
int32_t ssi_status; /* Exit status or signal (SIGCHLD) */
int32_t ssi_int; /* Integer sent by sigqueue(2) */
uint64_t ssi_ptr; /* Pointer sent by sigqueue(2) */
int32_t ssi_int; /* Integer sent by sigqueue(3) */
uint64_t ssi_ptr; /* Pointer sent by sigqueue(3) */
uint64_t ssi_utime; /* User CPU time consumed (SIGCHLD) */
uint64_t ssi_stime; /* System CPU time consumed (SIGCHLD) */
uint64_t ssi_addr; /* Address that generated signal
@ -352,7 +352,7 @@ In kernels before 2.6.25, the
and
.I ssi_int
fields are not filled in with the data accompanying a signal sent by
.BR sigqueue (2).
.BR sigqueue (3).
.\" The fix also was put into 2.6.24.5
.SH EXAMPLE
The program below accepts the signals

View File

@ -121,7 +121,7 @@ are generated
while they are blocked, the result is undefined,
unless the signal was generated by
.BR kill (2),
.BR sigqueue (2),
.BR sigqueue (3),
or
.BR raise (3).
.PP
@ -134,8 +134,8 @@ for details on manipulating signal sets.
.BR sigaction (2),
.BR signal (2),
.BR sigpending (2),
.BR sigqueue (2),
.BR sigsuspend (2),
.BR pthread_sigmask (3),
.BR sigqueue (3),
.BR sigsetops (3),
.BR signal (7)

View File

@ -177,7 +177,7 @@ is a library function implemented on top of
.BR signalfd (2),
.BR sigpending (2),
.BR sigprocmask (2),
.BR sigqueue (2),
.BR sigqueue (3),
.BR sigsetops (3),
.BR sigwait (3),
.BR signal (7),

View File

@ -80,7 +80,7 @@ the child process ID for
and the user ID and process ID of the sender, for signals set using
.BR kill (2)
or
.BR sigqueue (2)).
.BR sigqueue (3)).
The array \fIsys_siglist\fP holds the signal description strings
indexed by signal number.

View File

@ -44,7 +44,7 @@ _GNU_SOURCE
The
.BR pthread_sigqueue ()
function performs a similar task to
.BR sigqueue (2),
.BR sigqueue (3),
but, rather than sending a signal to another process,
it sends a signal to another thread in the same process as the
calling thread.
@ -58,7 +58,7 @@ argument specifies the signal to be sent.
The
.I value
argument specifies data to accompany the signal; see
.BR sigqueue (2)
.BR sigqueue (3)
for details.
.SH RETURN VALUE
On success,
@ -93,7 +93,7 @@ This function is a GNU extension.
.SH SEE ALSO
.BR rt_tgsigqueueinfo (2),
.BR sigaction (2),
.BR sigqueue (2),
.BR sigqueue (3),
.BR sigwait (3),
.BR pthread_sigmask (3),
.BR pthreads (7),

View File

@ -52,7 +52,7 @@ affected by the call, for example:
.BR setpgid (2),
.\" .BR getsid (2),
.BR setsid (2),
.BR sigqueue (2),
.BR sigqueue (3),
and
.BR waitpid (2).
.\" .BR waitid (2),

View File

@ -124,7 +124,7 @@ Sends a signal to a specified thread within a specific process.
(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
@ -386,7 +386,7 @@ By contrast, if multiple instances of a standard signal are delivered
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
@ -856,7 +856,6 @@ signal 29 is
.BR signalfd (2),
.BR sigpending (2),
.BR sigprocmask (2),
.BR sigqueue (2),
.BR sigsuspend (2),
.BR sigwaitinfo (2),
.BR abort (3),
@ -864,6 +863,7 @@ signal 29 is
.BR longjmp (3),
.BR raise (3),
.BR pthread_sigqueue (3),
.BR sigqueue (3),
.BR sigset (3),
.BR sigsetops (3),
.BR sigvec (3),