Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 47822 invoked by uid 500); 24 Aug 2000 13:12:54 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 47811 invoked from network); 24 Aug 2000 13:12:54 -0000 Message-ID: <053d01c00dcd$c1b05730$e4421b09@raleigh.ibm.com> From: "Bill Stoddard" To: References: Subject: Re: Apache spawning off wildly Date: Thu, 24 Aug 2000 09:18:13 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N We are missing logic in the parent to give up restarting the child. Here is how you can avoid a reboot... First, find the parent process PID in logs/httpd.pid. Then with the task manager, kill the parent process. If task manager will not let you kill the process, then attach the debugger to the process (through the task manager) then kill the debugger session. Ugly but it works for me. Bill Hi I have been playing around with Apache 2.0a6 and the NT mpm layer. (I am disabling the service interface.) Well, what happens is that I get a gpf because of my tinkering. Yes the error is my fault. But what what happens as a result of this error is that Apache wildy spawns off 1000+ processes that all gpf with the same error. I cannot stop this process because it goes like wildfire. The feeling I get is when Apache crashes, it notices the problem and spawns off another process because the original one crashed. The only way to stop the error is to reboot my W2K box. Could someone please help me stop this error since debugging this has become futile... Thanks... Christian