Date: Mon, 29 Sep 2003 08:35:20 +0200 From: "Devon H. O'Dell" <dodell@sitetronics.com> To: Philip Paeps <philip+freebsd@paeps.cx> Cc: security@freebsd.org Subject: Re: Apache under attack and eating resources? Message-ID: <3F77D2A8.10409@sitetronics.com> In-Reply-To: <20030929062920.GB760@hermes.nixsys.be> References: <20030928235939.GH629@hermes.home.paeps.cx> <20030929022753.GC334@silverwraith.com> <20030929062920.GB760@hermes.nixsys.be>
next in thread | previous in thread | raw e-mail | index | archive | help
>I forgot to mention I was running mod_php4 from the ports. I don't think any >scripts changed in the last few weeks, but I'll have a look into it. Any idea >what kind of script bugs could cause PHP to tear things down like this, other >than the classic loop from hell? > >Thanks! > > - Philip > > PHP does a pretty good job from protecting against this. Installing mod_php4 from ports will also turn on the --enable-memory-limit switch, which causes PHP to terminate if more than x MB RAM are taken (this shouldn't segfault Apache). The "classic loop from hell" should also be undoable, since PHP has a 60 second execution time limit. You might want to run your httpd process in gdb to see what's going on when stuff segfaults. If this is indeed a problem with PHP, I'm sure the developers would like to hear about it ASAP! --Devon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F77D2A8.10409>