ID: 2560
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Closed
Bug Type: Misbehaving function
Operating System: BSDI BSD/OS 4.0.1
PHP Version: 4.0 Beta 2
New Comment:
I doubt that - remember this is cpu time, not wall clock time.
sleep(10) doesn't count.
Previous Comments:
[2002-03-21 12:16:16] [EMAIL PROTECTED]
This bug is still present in PHP 4.1.2, exactly as described by djm
[1999-12-03 12:27:55] [EMAIL PROTECTED]
Fixed in CVS by Rasmus.
[1999-10-18 11:48:12] [EMAIL PROTECTED]
I'm using PHP 4.0B2 as a DSO with apache 1.3.9. In my httpd.conf I
have set
AddType application/x-httpd-php .php3
AddType application/x-httpd-php .php
php_admin_flag safe_mode On
php_admin_value doc_root "/homes/www141/webtest"
php_admin_value open_basedir "/homes/www141/webtest"
php_admin_value safe_mode_exec_dir "/homes/www141/webtest/bin"
php_flag log_errors On
php_value error_log "/homes/www141/webtest/logs/php.log"
php_value max_execution_time 3
php_value memory_limit 8388608
When I run the following PHP script, it is not aborted before printing
the
second message, despite having run for more than 3 seconds. And it
takes about 13-18 wall clock seconds before PHP aborts the infinite
loop. Printing
phpinfo() confirms that max_execution_time is indeed set to 3.
test of max_execution_time
\n"; sleep(10); echo "after\n";
while (1) { $i++; }
?>
This is being run on a 450MHz server that's doing nothing else, so I
don't
think CPU contention is an issue.
--
Edit this bug report at http://bugs.php.net/?id=2560&edit=1