If he was using set_time_limit() it should have overridden the max_execution_time configuration in php.ini though, right? It seems to work for me, I use set_time_limit(1000) in a few places (especially in the reports) of the app I'm working on right now and it seems to do just what http://www.php.net/manual/en/function.set-time-limit.php says it should.. Perhaps I'm doing something else different though... You should keep your money, these lists are here for such help! Good luck! -Mitch ----- Original Message ----- From: "Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx> To: <pgsql-php@xxxxxxxxxxxxxx> Sent: Friday, October 05, 2001 11:59 AM Subject: Re: [PHP] Help with timeouts > I think the assumption is incorrect. Is the browser reporting the timeout, > or is the webserver telling the browser it timed out? > > As an example of a difference, IE will display a local page saying the > connection timed out, whereas if the page is actually displayed by the > wbserver, it is the server that finally killed the connection. > > Again, as I said before, look at your php.ini file > > specifically this parameter: > > max_execution_time = 30 ; Maximum execution time of each script, in > seconds > > If a script takes longer than that number, it will kill it. This is to > prevent infinite loops. Up this number and you should be ok. > > I've had browsers that have sat for well over a minute on a stalled page. > > Again, breast cancer research for both donations. > > > > Adam Lang > Systems Engineer > Rutgers Casualty Insurance Company > http://www.rutgersinsurance.com > ----- Original Message ----- > From: "Josh Berkus" <josh@xxxxxxxxxxxx> > To: <pgsql-php@xxxxxxxxxxxxxx> > Sent: Friday, October 05, 2001 11:26 AM > Subject: Re: [PHP] Help with timeouts > > > > Folks, > > > > Some answers: > > > > > I have a very complex database operation that can sometimes take > > > 70-90 > > > seconds to return results. The web page which displays the results, > > > however, seems to always timeout at 60seconds despite setting the > > > Apache > > > timeout to 300 seconds and set_time_limit to 240. > > > > After a helpful web guru called us up from our post, we were able to > > diagnose what's happening here (donation to be announced later): > > > > Regardless of the Timeout and set_time_limit() settings, most browsers > > will time out at 60 seconds. > > > > This is obviously a huge annoyance. Therefore I am offering a *second* > > charity prize to any person who can give me code (PHP or Perl) which > > will display a "Processing" screen with an auto-reload to keep the > > browser interested while waiting 60 to 120 seconds for a database > > response in the background. *Someone* must have done this already, even > > though multi-threading in PHP & Perl is nigh impossible. > > > > -Josh Berkus > > > > > -------------------------------------------------------------------------- -- > ---- > > > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 4: Don't 'kill -9' the postmaster > > > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster >
