Return-Path: Delivered-To: apache-cvs-archive@hyperreal.org Received: (qmail 11830 invoked by uid 6000); 19 Apr 1999 04:49:21 -0000 Received: (qmail 11809 invoked by alias); 19 Apr 1999 04:49:17 -0000 Delivered-To: apache-apr-cvs@hyperreal.org Received: (qmail 11805 invoked by uid 216); 19 Apr 1999 04:49:16 -0000 Date: 19 Apr 1999 04:49:16 -0000 Message-ID: <19990419044916.11804.qmail@hyperreal.org> From: manoj@hyperreal.org To: apache-apr-cvs@hyperreal.org Subject: cvs commit: apache-apr STATUS Sender: apache-cvs-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org manoj 99/04/18 21:49:16 Modified: . STATUS Log: I like playing Alpha Centauri. Revision Changes Path 1.20 +7 -1 apache-apr/STATUS Index: STATUS =================================================================== RCS file: /home/cvs/apache-apr/STATUS,v retrieving revision 1.19 retrieving revision 1.20 diff -u -u -r1.19 -r1.20 --- STATUS 1999/04/09 02:31:21 1.19 +++ STATUS 1999/04/19 04:49:15 1.20 @@ -1,5 +1,5 @@ Apache Portable Runtime STATUS: -Last modified at [$Date: 1999/04/09 02:31:21 $] +Last modified at [$Date: 1999/04/19 04:49:15 $] Release: @@ -50,6 +50,12 @@ to the parent process rapidly (but not SIGWINCHes). The suspicion is that this is either an error in how pthread calls are used in the server, or a libc bug (the last refuge of a desperate programer). + + When the server runs at a high load, and the load later drops off, + the server tries to kill off some children. The problem is that the + children selected may have threads blocked on the accept lock, so + they will never exit. This wasn't a problem with 1.3, because each + process got kicked out of the lock with a signal. Open issues: