7 Aug
2010
7 Aug
'10
4:40 p.m.
On Sat, Aug 07, 2010 at 03:45:27PM +0000, Andy Smith wrote:
If you define "it happens" as "apache
using all my RAM and killing
my VPS" then yes I can imagine that is how it goes. However you
could add some monitoring to tell you when it's getting like that.
You could also set a ulimit on the amount of virtual memory that
apache can have, so it would just kill apache.
Or simply limit the number of apache processes in the apache config
file. I've had a couple of machines that have done this in the past,
and cutting down the number of copies of Apache that can be running at
any one time has solved it. The limits that Debian, for example, ship
with are massively over-sized for a small VPS.
I would suggest setting the MaxClients value (at least) to
something like 7, and the Min/MaxSpareServers values to 1-2.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Great oxymorons of the world, no. 3: Military Intelligence ---