mirror of https://github.com/mkerrisk/man-pages
Noted effect of RLIMIT_STACK resource limit for NPTL.
This commit is contained in:
parent
7fc594a121
commit
5e8b726f68
|
@ -273,6 +273,22 @@ However, a new thread's alternate signal stack settings
|
||||||
are copied from the thread that created it, so that
|
are copied from the thread that created it, so that
|
||||||
the threads initially share an alternate signal stack
|
the threads initially share an alternate signal stack
|
||||||
(fixed in kernel 2.6.16).
|
(fixed in kernel 2.6.16).
|
||||||
|
.PP
|
||||||
|
Note the following further points about the NPTL implementation:
|
||||||
|
.IP \- 3
|
||||||
|
If the stack size soft resource limit (see the description of
|
||||||
|
.B RLIMIT_STACK
|
||||||
|
in
|
||||||
|
.BR setrlimit (2))
|
||||||
|
is set to a value other than
|
||||||
|
.IR unlimited ,
|
||||||
|
then this value defines the default stack size for new threads.
|
||||||
|
To be effective, this limit must be set before the program
|
||||||
|
is executed, perhaps using the
|
||||||
|
.I ulimit -s
|
||||||
|
shell built-in command
|
||||||
|
.RI ( "limit stacksize"
|
||||||
|
in the C shell).
|
||||||
.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)
|
||||||
|
|
Loading…
Reference in New Issue