DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28473>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28473

RLimitCPU and RLimitMEM do not seem to work

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |



------- Additional Comments From [EMAIL PROTECTED]  2004-04-21 19:28 -------
Thanks for taking the time to test, I really appreciate that a lot! I checked
some more things, here some more results:

- Your script terminates fine after about five seconds. I've set two as a limit,
but I think the time is okay as it takes some time to close the PHP instance.
I've checked the status of the script via ps auxw | grep php.

- Your script terminates with "Premature end of script headers". No other error
message is shown in the logs. Is that correct or should Apache print out
something like "I've killed ID so and so"?

- On my test machine, I've set MaxClients to 20 and I couldn't kill the machine
anymore. This is only a workaround, as it knocks out a lot of users on higher
load machines, but at least it shows that MaxClients works for that.

- When a "normal access" (i.e. not my "attack") accesses a PHP script, the PHP
parser is only shown during the run of the script, checked with ps auxw | grep
php. However, when I "attack", it runs for quite a while several times. Possibly
for the 300 timeout seconds in httpd.conf, but I'll check that. "killall php" or
"killall -9 php" doesn't help. However, shutting down Apache brings down the PHP
interpreters, so I think that Apache just "forgets" about the running instances
when it is flooded and cannot handle them anymore.

Do you have any idea? Do you need more information? Again, thanks so much for
taking the time!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to