Return-Path: Mailing-List: contact modperl-help@apache.org; run by ezmlm Delivered-To: mailing list modperl@apache.org Received: (qmail 41350 invoked from network); 1 Jun 2000 22:13:22 -0000 Received: from frag.lach.net (206.196.40.50) by locus.apache.org with SMTP; 1 Jun 2000 22:13:22 -0000 Received: from localhost (jay@localhost) by frag.lach.net (8.9.3+Sun/8.9.1) with ESMTP id RAA10629 for ; Thu, 1 Jun 2000 17:12:25 -0500 (CDT) X-Authentication-Warning: frag.securenets.com: jay owned process doing -bs Date: Thu, 1 Jun 2000 17:12:25 -0500 (CDT) From: Jay Jacobs X-Sender: jay@frag To: modperl@apache.org Subject: Apache children hanging (not exiting) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N With that previous thread of Apache children hanging up the server it made me think of an issue I see quite frequently in development... When I stop the mod_perl server, it won't exit properly (or fast) : [warn] child process 8530 still did not exit, sending a SIGTERM (multiplied by number of processes) I've seen this on servers running really sloppy code as well as really tight code (but a lot of it). Eventually the children do die off, but it takes about 15 seconds... Could this be related to the aforemented thread? Jay Jacobs