Re: CLI & max_execution_time

On Sun, Mar 24, 2002 at 03:40:10PM +0100, Marcus Börger wrote : > At 15:32 24.03.2002, Markus Fischer wrote: > >On Sun, Mar 24, 2002 at 03:04:18PM +0100, Marcus Börger wrote : > >> I do not think it is a good idea to have many 'special ways' in cLI. > >> Such as always registering argc/argv we have already. For me > >> i would more likly have a special section in php.ini to set all this. > > > > You don't seem to undertand. CLI _is_ special. It lives in > > another environment then the apache/cgi SAPI does. > > Of cause i do - [...] I don't think so, I'm sorry. ;-) > > How come you think treating the CLI version the same is a > > good idea when they in fact have to work under very different > > environments/conditions ? > > Using a special section for CLI would allow providing such different > conditions. In fact this is something which has to be entirely discussed too. No propose, no (real) plan has yet been made how/if to manage those different SAPIs configurations in the future. > > Would you EVER expect a bash/perl/awk/sed/python/nameit > > script by >default< only run a certain amount of time, namely > > it's maximum execution time ? Certainly not. > > No i don't but is a feature we have so why not disable it by default > ini entry instead of implementing a work around? Because specifically *I* and certainly other would not expect a shell scripting language to only run for about 30 seconds because the proper ini file is not present! Such a dependency is idiocy. - Markus -- Please always Cc to me when replying to me on the lists. GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc