On 06:59, Eric Covener wrote:
I might be able to shed a little light into this dark corner. (I found this out the hard way in a different context.*) Under Linux and similar OSs (but NOT windows), the PHP time limit applies to *User CPU* time only. It does not include system CPU time or any of the myriad varieties of wait time. So OP's loop around sleep will take a looooong time (but not literally forever) to eat up 300 secs or whatever of user cpu.On Mon, Jun 20, 2011 at 9:26 AM, Zaccone, Warren<wzaccone@xxxxxxxxxxxxx> wrote:yes. so I am I. The default setting is 30 seconds however pstack shows all 256 children running this script indefinitely - until I stop and restart httpd. This statement in the php doc is leading me to believe the Timeout directive will override: " Your web server can have other timeout configurations that may also interrupt PHP execution. Apache has a Timeout directive and IIS has a CGI timeout function. Both default to 300 seconds. See your web server documentation for specific details."FWIW, if you were running PHP as CGI, and not trickling back some input in that loop, Apache's CGI module would give up based on the Timeout. But since you run mod_php, nobody but PHP is watching the clock.
* I got bitten by the converse - a PHP maintenance script in Drupal was getting timed out (wallclock time) on a Windows server because of I/O wait time.
HTH Peter --------------------------------------------------------------------- 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@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|