Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 12831 invoked from network); 31 Jul 2009 10:31:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Jul 2009 10:31:31 -0000 Received: (qmail 13873 invoked by uid 500); 31 Jul 2009 09:32:27 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 13842 invoked by uid 500); 31 Jul 2009 09:32:26 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 13822 invoked by uid 99); 31 Jul 2009 09:32:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jul 2009 09:32:24 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of shibi.ns@gmail.com designates 74.125.92.147 as permitted sender) Received: from [74.125.92.147] (HELO qw-out-1920.google.com) (74.125.92.147) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jul 2009 09:32:15 +0000 Received: by qw-out-1920.google.com with SMTP id 5so1779082qwc.40 for ; Fri, 31 Jul 2009 02:31:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=gJKQ/5GkgEnAbhs5CdwkJDP6PrOECbzcJvw7mqeee5M=; b=o7AKkEzZsmM4BV4FbhinMo8a3Mxn7fKi22ozQxl0OnXNt4fN5lpb3jrgl0c0+tzWpF N+kkBeH6E2V0vdkGFrk7vw8mkUS+9QWAPagCpEfZAiXuqxCPDBmEOhrjV1ZHJMRzev89 HgjpoHu6V/5TZgIpEgCBDyCL21jHq7l4ec2Lc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=mflSaI2PB9vwlpFpe9gaHttZsAr4q3HqtcOzU6u51LTLu83qeEnR3/GxDRNEgvo0Nf 7mgLkWOtuRF4bt66Yu+edLtBsDs7GeHrT0NG3q22NqKCiSaLsSCF8GOjY4fGBXupY4IP frFVddrvlxMkGiLpJDhOiPG1ETPAOlIlpNQwA= MIME-Version: 1.0 Received: by 10.229.74.212 with SMTP id v20mr433529qcj.16.1249032715108; Fri, 31 Jul 2009 02:31:55 -0700 (PDT) Date: Fri, 31 Jul 2009 15:01:55 +0530 Message-ID: <672858890907310231v77aba052g89c2a306503260a8@mail.gmail.com> Subject: Apache2::Resource - What happens when the resource limit is consumed by the process From: Shibi NS To: modperl@perl.apache.org Content-Type: multipart/alternative; boundary=00163646c0044c026a046ffd17ef X-Virus-Checked: Checked by ClamAV on apache.org --00163646c0044c026a046ffd17ef Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit We can use Apache2::Resource to RSS and Memory,etc usage by the process . - What happens when the resource limit setting is reached and it requires more resource? For example I sets the RSS to 70 M , but due to some bugs one of the process requires 80 M how does the systems handles it ? --Shibi Ns-- --00163646c0044c026a046ffd17ef Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
We can use Apache2::Resource to RSS and Memory,etc usage by the process= .=A0 - What happens when the resource limit setting is reached and it requ= ires more resource?

For example I sets the RSS=A0 to 70 M , but due = to some bugs one of the process requires 80 M how does the systems handles = it ?


--Shibi Ns--
--00163646c0044c026a046ffd17ef--