Re: Problem with timeout
| From: | Frank Arensmeier | Date: | Sat, 05 May 2007 08:34:43 +0000 |
| Subject: | Re: Problem with timeout | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-254464@lists.php.net to get a copy of this message | ||
4 maj 2007 kl. 23.48 skrev Richard Lynch:
On Fri, May 4, 2007 3:42 pm, Frank Arensmeier wrote:You are absolutely right. I might also mention that running the script under PHP CLI did two things: 1) No problems with timeout settings anymore. 2) The script takes 10 minutes less time to finish However, I realized that PHP CLI is version 4.4.4 whereas the Apache module PHP is version 5.something. After some modifications to the script, it is running flawlessly now.I still think that the best way to go is to not involve Apache at all when running the script. Because the script already has functions for output logging etc. it is no big deal to change the code so that it can be run from PHP CLI.Once you said it was something you did weekly, it's pretty much a given that you ought to use a cron job with PHP CLI and take Apache out of the picture entirely...
Actually, even if it's for surfer interaction, anything taking that long should probably be turned into a "jobs" oriented architecture, and queue up the work for a cron job later, with user email notification when it's done. NOBODY wants to sit that long watching the browser do nothing.I totally agree. The script was never ment to be user-triggered. Instead, the archiving process takes place weekly. Thanks you all! Have a nice weekend. //frank
--Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So?