Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 44802 invoked from network); 6 Jul 2007 20:42:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Jul 2007 20:42:29 -0000 Received: (qmail 29773 invoked by uid 500); 6 Jul 2007 20:42:23 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 29373 invoked by uid 500); 6 Jul 2007 20:42:22 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 29362 invoked by uid 99); 6 Jul 2007 20:42:22 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2007 13:42:22 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of hamilton@i2.com.br designates 201.30.166.136 as permitted sender) Received: from [201.30.166.136] (HELO luderitz.i2.com.br) (201.30.166.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2007 13:42:15 -0700 Received: from lima.i2.com.br (lima.i2.com.br [200.229.0.62]) by luderitz.i2.com.br (Postfix) with ESMTP id 4154F14F813E for ; Fri, 6 Jul 2007 17:41:54 -0300 (BRT) Date: Fri, 6 Jul 2007 17:41:54 -0300 (BRT) From: Hamilton Vera To: users@httpd.apache.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] dealing with CPU hogs Maybe you can monitor the CGI's with mod_perl and setting pam/system limits to apache user. []'s Hamilton Vera int Administrator (char Network[],char ComputationalSystems[]); http://antispam.br/ "Google is my shepherd, no want shall I know" On Fri, 6 Jul 2007, Tony Rice \(trice\) wrote: > Any suggestions on configuration changes I can make to lessen the impact of CGI scripts which become CPU hogs? > > I'm running an apache server with about 150 virtual servers. Ocassionally an errant script will go nuts and consume 100% of the CPU. It's really bad when a spider finds one of these poorly written scripts and calls it a few thousand times. > > I'm monitoring the server and killing off processes that run too long, that catches most issues before they impact performance too badly, but not when a spider is behind the requests.. Any other suggestions? Can consistent connections be throttled on a per client IP address basis? Can server processes be controlled on a per virtual server basis? > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org