https://bugzilla.kernel.org/show_bug.cgi?id=76101 --- Comment #1 from Michael Kerrisk <mtk.manpages@xxxxxxxxx> --- On 05/13/2014 07:22 PM, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=76101 > > Bug ID: 76101 > Summary: [TRIVIAL] PTHREAD_CREATE(3): EAGAIN and pid_max > Product: Documentation > Version: unspecified > Hardware: All > OS: Linux > Status: NEW > Severity: normal > Priority: P1 > Component: man-pages > Assignee: documentation_man-pages@xxxxxxxxxxxxxxxxxxxx > Reporter: carstengrohmann@xxxxxx > Regression: No > > Hi, > > The system-wide limit on the number of threads can also reached by a small > value in /proc/sys/kernel/pid_max. E.g. RHEL5 and RHEL6 systems uses a default > of 32768 in pid_max probably for compatibility with 32bit applications. > > This causes an EAGAIN also if the number of threads is significant lower than > thread-max or RLIMIT_NPROC. > > Please extent the EAGAIN statement to reflect pid_max too. Hello Carsten. Thanks for the report. I've added pid_max to the list of causes for EAGAIN in pthread_create(3). (And I've made the fork(2) text match that in pthread_create(3) as well.). Cheers, Michael -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
