ID: 37408 Updated by: [EMAIL PROTECTED] Reported By: Jared dot Williams1 at ntlworld dot com -Status: No Feedback +Status: Feedback Bug Type: Scripting Engine problem Operating System: Win2000 PHP Version: 5.1.4 Assigned To: helly New Comment:
Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.2-win32-latest.zip Previous Comments: ------------------------------------------------------------------------ [2006-05-25 01:00:00] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2006-05-19 08:05:50] psadac at gmail dot com it's a bug. I run php 5.1.4 over Windows XP, i have max_execution_time = 240 in my php.ini, set_time_limit(0) in my php script and i get "Maximum execution time of 60 seconds exceeded". ------------------------------------------------------------------------ [2006-05-18 13:42:54] mlee at kanhan dot com It's 30 seconds in my php.ini, but the error I get is this: "Fatal error: Maximum execution time of 60 seconds exceeded" Anyway, I thought the documentation is quite clear about the fact max_execution_time is one of the overridden php.ini directives for the CLI executable and that the default value is 0 (infinite). ------------------------------------------------------------------------ [2006-05-17 14:06:28] [EMAIL PROTECTED] What's defined for max_execution_time in your php.ini ------------------------------------------------------------------------ [2006-05-16 19:58:11] mlee at kanhan dot com It IS a bug. I've double-checked the documentation: http://www.php.net/manual/en/features.commandline.php It says the default value of max_execution_time is 0 for the CLI version. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/37408 -- Edit this bug report at http://bugs.php.net/?id=37408&edit=1
