that seems to be related to http://bugs.php.net/bugs.php?id=8414
I was told that on windows max_execution_time is what most people expect
while on
linux it is the maximum CPU time.
and please do something to make it possible to check for "maximum
execution time exceeded" condition
in registerd s
So, we need to say is something to the effect of:
The max_execution_time directive and set_time_limit function act to
limit
the amount of time that a PHP script is allowed to execute. This is not
necessarily the same as the amount of time that the script is allowed to
run. If the
Right - as I said, the executed program will go on running, whereas the
script will terminate...
At 01:44 16/1/2001, Zak Greant wrote:
>Zeev Suraski wrote:
> > BTW, offhand, I'm not sure that it's really not working. The time limit
> > should still be imposed (at least under UNIX, not under Win
Zeev Suraski wrote:
> BTW, offhand, I'm not sure that it's really not working. The time limit
> should still be imposed (at least under UNIX, not under Windows).
However,
> the executed program will go on running.
I did a very basic test:
The script runs, exiting with this message
BTW, offhand, I'm not sure that it's really not working. The time limit
should still be imposed (at least under UNIX, not under Windows). However,
the executed program will go on running.
Zeev
At 07:17 15/1/2001, Zak Greant wrote:
>A recent note added to the manual errata pointed out the
>se
Yeah, that's a good idea (to document it).
Zeev
At 07:17 15/1/2001, Zak Greant wrote:
>A recent note added to the manual errata pointed out the
>set_time_limit does not affect system commands that have
>been executed by PHP.
>
>I would guess that attempting to limit system behavior in
>this way
