Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 1260 invoked by uid 500); 17 Apr 2001 20:34:35 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 1206 invoked from network); 17 Apr 2001 20:34:29 -0000 Sender: rederpj@raleigh.ibm.com Message-ID: <3ADCA851.F9B5316B@raleigh.ibm.com> Date: Tue, 17 Apr 2001 16:32:17 -0400 From: "Paul J. Reder" X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14-15mdksecure i686) X-Accept-Language: en MIME-Version: 1.0 To: new-httpd@apache.org Subject: Re: Apache 2.0.17 tarballs up References: <010101c0c770$763c6cf0$e4421b09@raleigh.ibm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Bill Stoddard wrote: > > Doug reported some shutdown problems right after the tag, so this is probably not a good beta > candidate. If you disagree, please VOTE! > > Bill I saw some cases where the kids were slow to shut down during testing. What I found was that since the kids are not shutdown directly via signal, but indirectly via flag, some of the kids took a little longer than before. The kids a now allowed to finish their processing. This is the nature of the fix to avoid the deadlock that occurred when they were shutdown immediately. This is why I shifted the point in the switch statement to delay the time period before Apache complained and SIGTERMed (or SIGKILLed) again. In my tests, the kids eventually went down. The messages and extra kills were mostly just an annoyance. -- Paul J. Reder ----------------------------------------------------------- "The strength of the Constitution lies entirely in the determination of each citizen to defend it. Only if every single citizen feels duty bound to do his share in this defense are the constitutional rights secure." -- Albert Einstein