Gregory Davis gregdavis at ieee.org
Thu Dec 29 12:51:11 CST 2005

Actually, the variable is PTHREAD_THREADS_MAX (notice the extra S) and is =

in /usr/include/bits/local_lim.h.  My header undefines it and comments that =

there should be no limit (that seems like an DoS vulnerability for software =

that doesn't keep its own max number of threads).  There is a =

_POSIX_THREAD_THREADS_MAX defined just prior in the same file, that is set =
to =

64.  See this thread: =

ex_html?fullMode=3D1.  =

Also, other mailing lists describe a bug in RH 7.3 where the macro was =

defined in the user-space header, but when compiling glibc, the value was =

ignored.  The effect was that only 254 or 255 threads were possible, =

indicating that glibc defined the macro as 255 or such, at compile time.

Disclaimer:  I have never worked with threads outside of Java/.NET/win32.


On Thursday 29 December 2005 13:07, Grindell, Joan M. wrote:
> If anyone is familiar with the Red Hat kernel, would you know the answer
> to this question:
> We are running Red Hat AS version 4 update1.  Our users have asked me
> what the PTHREAD_THREAD_MAX value is.  The kernel was installed from the
> Red Hat installation discs.  Is there a command or a location on the
> server that will yield this information?
> Many thanks,
> And a happy new year.
> Joan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://calug.com/pipermail/lug/attachments/20051229/6221d446/attachme=

More information about the lug mailing list