Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of jslive@gmail.com designates
 72.14.204.233 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=WrW7iQ4l0alcbq2kWBcZ6s6HLf6IZ1awEkdOv17abUomKZw13rTnZ10aF+eleRYrwMkVsCbad3ydC9CGrd8rHBZlZ5jKApwcFcfC8z+3giUK4eLy55YHxCwp7jZtMiCURaQRcaZXjpXjzO9TCtfgm707qR9vThTMafBZTuVVS8I=
Message-ID: <e498c1660712271216o65a5bf7co1065254a520d55f9@mail.gmail.com>
Date: Thu, 27 Dec 2007 14:16:56 -0600
From: "Joshua Slive" <joshua@slive.ca>
Sender: jslive@gmail.com
To: users@httpd.apache.org
In-Reply-To: <5f0f8dba0712261112n77ccdfbbxbdf4f782273e303b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5f0f8dba0712171124k1a7b9debh3c3f6fcf31f258a1@mail.gmail.com>
	 <e498c1660712171133i361f2725o22d6092ce24155ef@mail.gmail.com>
	 <5f0f8dba0712171234v6476281jb66fa3da3e2505d7@mail.gmail.com>
	 <e498c1660712171330j41f05c40u4ffd180bc23d9138@mail.gmail.com>
	 <5f0f8dba0712180604s2494deefjca33416e2f7e98df@mail.gmail.com>
	 <e498c1660712180636w60e9aa95v23298feb05e32f7f@mail.gmail.com>
	 <5f0f8dba0712240536i79c2938co6853e490d16363ec@mail.gmail.com>
	 <5f0f8dba0712240648l44dc3813v37e99a48e067d090@mail.gmail.com>
	 <e498c1660712240805i69b37f35h75138e99c973872a@mail.gmail.com>
	 <5f0f8dba0712261112n77ccdfbbxbdf4f782273e303b@mail.gmail.com>
Subject: Re: [users@httpd] apache freezes the virtual machine.

On Dec 26, 2007 1:12 PM, Asrai khn <asraikhn@gmail.com> wrote:
>
>
>
> On Dec 24, 2007 9:05 PM, Joshua Slive <joshua@slive.ca> wrote:
> > Anyway, what that tells you is that one of those scripts is likely the
> > culprit that is gobbling down all the memory in your box. Take a look
> > at all the scripts that were being requested and see if you can figure
> > out what is going wrong.
>
> Joshua,
>
> Ok we are moving the faulty site off our shared web  server to dedicated
> hosting.
>
> However Also, need to figure how to protect ourself better against this kind
> of
> thing on shared webs. Limiting resource usage of apache spawned user
> processes via apache config options?

Not when you are running scripting engines in the same process as the
web server.

Here are some notes on the general issue of privelege separation.
Resource limitting is a different, but quite related issue with
similar solutions.
http://wiki.apache.org/httpd/PrivilegeSeparation

In general, if you need resource limitting you should get the
scripting engines out of the web server process, either by using
cgi/fast-cgi, or by running multiple web server instances.

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> 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