pthreads.7: Add ref to signal(7) for further info on use of real-time signals

signal(7) provides some further details on the use of real-time
signals by the two Linux threading implementations.

Signed-off-by: Michael Kerrisk <michael.kerrisk@gmail.com>
This commit is contained in:
Michael Kerrisk 2008-11-18 08:42:20 -05:00
parent 222d90f4e9
commit 8bfd40a95e
1 changed files with 8 additions and 3 deletions

View File

@ -21,7 +21,7 @@
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\"
.TH PTHREADS 7 2008-11-11 "Linux" "Linux Programmer's Manual"
.TH PTHREADS 7 2008-11-18 "Linux" "Linux Programmer's Manual"
.SH NAME
pthreads \- POSIX threads
.SH DESCRIPTION
@ -672,7 +672,9 @@ This thread handles thread creation and termination.
(Problems can result if this thread is inadvertently killed.)
.IP \- 3
Signals are used internally by the implementation.
On Linux 2.2 and later, the first three real-time signals are used.
On Linux 2.2 and later, the first three real-time signals are used
(see also
.BR signal (7)).
On older Linux kernels,
.B SIGUSR1
and
@ -769,7 +771,9 @@ With NPTL, all of the threads in a process are placed
in the same thread group;
all members of a thread groups share the same PID.
NPTL does not employ a manager thread.
NPTL makes internal use of the first two real-time signals;
NPTL makes internal use of the first two real-time signals
(see also
.BR signal (7));
these signals cannot be used in applications.
NPTL still has at least one non-conformance with POSIX.1:
@ -875,6 +879,7 @@ bash$ $( LD_ASSUME_KERNEL=2.2.5 ldd /bin/ls | grep libc.so | \\
.BR gettid (2),
.BR proc (5),
.BR futex (7),
.BR signal (7),
.br
and various Pthreads manual pages, for example:
.BR pthread_attr_init (3),