The NPTL limitation that only the main thread could call

setsid() and setpgid() was removed in 2.6.16.
This commit is contained in:
Michael Kerrisk 2006-03-05 09:00:21 +00:00
parent e91fec0909
commit 2e17464853
1 changed files with 9 additions and 14 deletions

View File

@ -249,20 +249,6 @@ are copied from the the thread that created it, so that
the threads initially share an alternate signal stack. the threads initially share an alternate signal stack.
.IP \- 3 .IP \- 3
Threads do not share a common nice value. Threads do not share a common nice value.
.IP \- 3
Only the main thread is permitted to start a new session using
.BR setsid (2).
.\" FIXME why is only the main thread permitted to
.\" start a new session using setsid()?
.\" Perhaps fixed in 2.6.16?
.\"
.IP \- 3
Only the main thread is permitted to make the process into a
process group leader using
.BR setpgid (2).
.\" FIXME why is only the main thread permitted to make the
.\" process into a process group leader using setpgid()?
.\" Perhaps fixed in 2.6.16?
.PP .PP
Some NPTL non-conformances only occur with older kernels: Some NPTL non-conformances only occur with older kernels:
.IP \- 3 .IP \- 3
@ -275,6 +261,15 @@ is per-thread rather than process-wide (fixed in kernel 2.6.9).
Threads do not share resource limits (fixed in kernel 2.6.10). Threads do not share resource limits (fixed in kernel 2.6.10).
.IP \- 3 .IP \- 3
Threads do not share interval timers (fixed in kernel 2.6.12). Threads do not share interval timers (fixed in kernel 2.6.12).
.IP \- 3
Only the main thread is permitted to start a new session using
.BR setsid (2)
(fixed in kernel 2.6.16).
.IP \- 3
Only the main thread is permitted to make the process into a
process group leader using
.BR setpgid (2)
(fixed in kernel 2.6.16).
.SS "Determining the Threading Implementation" .SS "Determining the Threading Implementation"
Since glibc 2.3.2, the Since glibc 2.3.2, the
.BR getconf (1) .BR getconf (1)