manoj 99/05/25 21:04:32
Modified: . STATUS Log: 64 * 8 > 256. Linux was hitting user process limits. Revision Changes Path 1.26 +7 -7 apache-apr/STATUS Index: STATUS =================================================================== RCS file: /home/cvs/apache-apr/STATUS,v retrieving revision 1.25 retrieving revision 1.26 diff -u -u -r1.25 -r1.26 --- STATUS 1999/05/25 05:49:27 1.25 +++ STATUS 1999/05/26 04:04:32 1.26 @@ -1,5 +1,5 @@ Apache Portable Runtime STATUS: -Last modified at [$Date: 1999/05/25 05:49:27 $] +Last modified at [$Date: 1999/05/26 04:04:32 $] Release: @@ -43,12 +43,12 @@ Needs patch: - With Linux 2.2.9 + glibc 2.1.1pre (from RH 6), if MaxRequestsPerChild - is low (e.g. 5) and ThreadsPerChild is high (e.g. 64), some processes - will hang in pthread_create. This is an insane configuration, though. - - With AIX 4.2, if MaxRequestsPerChild is low and ThreadsPerChild is - high, the signal delivered to sigwait gets dropped on the floor. + With AIX 4.2, if MaxRequestsPerChild is low (e.g. 5) and + ThreadsPerChild is high (e.g. 64), the signal delivered to sigwait + gets dropped on the floor. The hypothesis is that the signals blocked + by pthread_sigmask aren't kept pending as they should be, so when + worker threads exit quickly and signal the sigwait thread before the + sigwait() call has been entered, the thread never gets the signal. Open issues:
