Web execution is bound with the execution time limit in php.ini and it causes 500 internal server error upon the prescribed end of the span.

My question is if the CLI, or Command Line Interface SAPI does the same thing with my script? I have a script that may very well run dozens of hours before it finishes its job.

As of PHP 4.3 (at least) the maximum execution time default is not limited. Check out http://us3.php.net/features.commandline

Just to be on the safe side, I've always set a number of parameters using ini_set, including max_execution_time, memory_limit, mysql_connect_timeout, and a few more when calling php scripts from CLI/cron.

As of PHP 4.3 (at least) the maximum execution time default is not limited. Check out http://us3.php.net/features.commandline

Just to be on the safe side, I've always set a number of parameters using ini_set, including max_execution_time, memory_limit, mysql_connect_timeout, and a few more when calling php scripts from CLI/cron.

Nice info and suggestion. I tested it a little bit on my host and it turned out to be no time limit on console command.

ini_get is a neat one that will come handy in many situations, but is it also for this reason prohibitied by hosters?

Originally Posted by yangyang

ini_get is a neat one that will come handy in many situations, but is it also for this reason prohibitied by hosters?

Good question. Honestly, I don't know -- I'm not in the hosting business and haven't used a shared server in nearly a decade -- back then I was doing most web apps in Perl or C/C++. I'm sure someone else here can give you an idea as to the why on that!