Re: [PATCH] Raise warning first on "Maximum execution time exceeded"
| From: | troels knak-nielsen | Date: | Mon, 22 Mar 2010 15:22:56 +0000 |
| Subject: | Re: [PATCH] Raise warning first on "Maximum execution time exceeded" | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-47448@lists.php.net to get a copy of this message | ||
2010/3/22 Johannes Schlüter <johannes@php.net>:
> A one second delay is no option there. And what actually happens is that
> the warning triggers your custom error handler. After that it sleeps
> then it dies.
What do you mean by "no option"? Otherwise yes, that's what it does.
> This also creates a "nice" way to extend the script runtime after the
> timeout occurred. aka. making the timeout useless for many scenarios it
> was meant for.
I'm not sure I understand. Are you implying that it is somehow
possible to circumvent the second (fatal) error with this change? How?
--
troels