Return-Path: 
 <users-return-66766-apmail-httpd-users-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-users-archive@www.apache.org
Received: (qmail 45885 invoked from network); 20 Sep 2006 08:20:57 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 20 Sep 2006 08:20:57 -0000
Received: (qmail 28664 invoked by uid 500); 20 Sep 2006 08:20:33 -0000
Delivered-To: apmail-httpd-users-archive@httpd.apache.org
Received: (qmail 28582 invoked by uid 500); 20 Sep 2006 08:20:33 -0000
Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
list-help: <mailto:users-help@httpd.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@httpd.apache.org>
List-Post: <mailto:users@httpd.apache.org>
List-Id: <users.httpd.apache.org>
Delivered-To: mailing list users@httpd.apache.org
Received: (qmail 28560 invoked by uid 99); 20 Sep 2006 08:20:33 -0000
X-ASF-Spam-Status: No, hits=3.4 required=10.0
	tests=DNS_FROM_RFC_ABUSE,HTML_10_20,HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of steve.j.swift@gmail.com
 designates 66.249.82.234 as permitted sender)
Received: from [66.249.82.234] (HELO wx-out-0506.google.com) (66.249.82.234)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Sep 2006 01:20:32 -0700
Received: by wx-out-0506.google.com with SMTP id s19so175791wxc
        for <users@httpd.apache.org>; Wed, 20 Sep 2006 01:20:12 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=OZ3KyRJJAxTgxsRT+dKZfMzTNFt438T2ud5cUdnvPV090xCh7AQneqjCPZsxhcj/cyJRIvDJpfNrGOJPkaLb2XfJ0khdKH3YzaEnCorhU7RSTq618h8GL6FzKtEiYVGiWdNitxsdrP3+Gv3mZ+1XdW5VIs14+jw3WP5bQ3v8Zr4=
Received: by 10.90.105.19 with SMTP id d19mr6156427agc;
        Wed, 20 Sep 2006 01:20:12 -0700 (PDT)
Received: by 10.90.96.14 with HTTP; Wed, 20 Sep 2006 01:20:12 -0700 (PDT)
Message-ID: <dbd3c1650609200120p5fd77465mb90149f0dbd69c2@mail.gmail.com>
Date: Wed, 20 Sep 2006 09:20:12 +0100
From: "Steve Swift" <steve.j.swift@gmail.com>
To: users@httpd.apache.org
In-Reply-To: 
 <FDD5D99066749040AF9098A720E989770377FEC9@CIWMEXZSA0E.ex.ordersx.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_65721_23829331.1158740412060"
References: 
 <FDD5D99066749040AF9098A720E989770377FEC9@CIWMEXZSA0E.ex.ordersx.org>
X-Virus-Checked: Checked by ClamAV on apache.org
Subject: Re: [users@httpd] CGI Timeouts?
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

------=_Part_65721_23829331.1158740412060
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

> But apache won't (can't!) kill the process that's looping...

The operating system is Linux. The separate threads are spawned as "apache"
(in our case) but there is still the root process running httpd - that
should have no problems killing of looping CGI processes, if it wanted to.

However, I'll accept that "It cannot be done" and continue monitoring for
looping apache processes.

If I get motivated I could probably write a cron task to inspect the
/server-status webpage every two minutes and to kill off any thread that
seems to be hogging the system.

-- 
Steve Swift
http://www.swiftys.org.uk

------=_Part_65721_23829331.1158740412060
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

&gt; But apache won't (can't!) kill the process that's looping...<br><br>The operating system is Linux. The separate threads are spawned as &quot;apache&quot; (in our case) but there is still the root process running httpd - that should have no problems killing of looping CGI processes, if it wanted to.
<br><br>However, I'll accept that &quot;It cannot be done&quot; and continue monitoring for looping apache processes.<br><br>If I get motivated I could probably write a cron task to inspect the /server-status webpage every two minutes and to kill off any thread that seems to be hogging the system.
<br><br>-- <br>Steve Swift<br><a href="http://www.swiftys.org.uk">http://www.swiftys.org.uk</a>

------=_Part_65721_23829331.1158740412060--