I wonder at what kind of script you have, that needs to be run
absolutely nonstop 24/7, but I'll share some "wild guesses":
1. It is not run by a web server, otherwise it would timeout the
server (which doesn't mean that it doesn't have relation with your web
pages). Your 24/7 script is being command-line launched with no direct
relation with the web server. Is that so?
2. Either you're using the set_time_limit to an unbelievably high
value or your script is being executed on a loop, once and again, but
running fresh new once in a while. Otherwise, how do you manage PHP
not timing out on your 24/7 script?
3. Is your script so critical that it absolutely can't be stopped for
a fraction of a second, just te be launched again, and so, refreshing
your modules.
Maybe having at least some idea of what you're trying to accomplish
would lead to better suggestions (instead of just feelings or wild
guesses ;) ).
Gonzalo.
> In article <003e01c0852c$b4236e50$064af2d4@kill9>, kill-9 <kill-9@kill-
9.dk>> writes
>>btw thanks for all your feelings. having someone to hash this out with is
>>helping.
> If someone has a cached copy of your page in their browser / their proxy
> server cache / their ISP's proxy server cache / etc, I don't know of any
> *guaranteed* way of flushing it out from the server (with some browsers,
> you can't even guarantee that using the 'reload' button will flush
> everything out...).
> Having said that, I develop on a single machine running Apache, PHP, and
> browser. Any time I change any bit of source code, all I need to do is
> press the 'reload' button on the browser and I always pick up the latest
> version of all the modules.
> Anything more than that ... you're in the hands of the gods.
> Good luck - John
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
