Darren Gamble wrote: This is probably just one of those cases that by the time the application determines that its child has exceeded its configured limits in resources, there are not enough resources (memory in this case) left to do the housekeeping and kill off the child.
An acceptable algorithm to handle this might be difficult, namely, Apache would possibly have to keep track of the amount of heap left to it, make a difficult decision to kill the child before it exceeded its configured limits. In the mean time, sendmail, running on the same machine as Apache, grabs a bunch of memory and Apache, doing its best with what it thinks is available, gets screwed anyway with its new, sophisticated algorithm. Sendmail dies too. Maybe kerneld dies too. The machine dies. Er, I'll leave this to the CS researchers. We ain't gonna solve problems like this. I am not even sure this is worth a bug report... If there could be a moral to this thread, it is, go buy a few more Gigs of memory. _justin ======================= > > Good day, > > Just reading this thread, figured I would put my $0.02 in. > > This is apparently a known problem. It seems to occur whenever the php > script uses lots of memory, actually, and it does the same thing whether > it's run standalone or as a module. > > I first experienced it when I had a PHP script load a 10 meg LDAP database > into memory, which took some 90 Megs of RAM to do (overhead, I guess). If I > ran the script standalone, it wouldn't quit right away. If it was run as a > module, Apache would have to kill the child off (it logged this activity) if > I asked Apache to shut down. If I ran the script a few times, all of the > memory of the machine would be used up, and I'd have to kill off Apache to > get it back. > > ============================ > Darren Gamble > Planner, Regional Services > Shaw Cablesystems GP > 630 - 3rd Avenue SW > Calgary, Alberta, Canada > T2P 4L4 > (403) 781-4948 > > -----Original Message----- > From: Jason Soza [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 18, 2002 12:10 AM > To: [EMAIL PROTECTED] > Subject: RE: [PHP] Nasty DoS in PHP > > Mine produced the same error message as yours, Jason, but the memory and CPU > usage continued until I hit the 'stop' button on the browser. It seemed to > have overridden both time and memory limits, as it had racked up 320 megs of > my RAM by the time I stopped it. > > Jason > > -----Original Message----- > From: Jason Murray [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 17, 2002 9:57 PM > To: 'CC Zona'; [EMAIL PROTECTED] > Subject: RE: [PHP] Nasty DoS in PHP > > > So that was both as an Apache mod and a CGI binary? Sounds like it's > > reproducible. > > Running as an Apache module here, it terminated as expected at 30 seconds. > > Jason > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php -- Justin Farnsworth Eye Integrated Communications 321 South Evans - Suite 203 Greenville, NC 27858 | Tel: (252) 353-0722 -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
