Re: CLI and php.ini

J Smith wrote: *SNIP*

I've also run into problems with a few extensions that don't run with things like the Zend optimizer. (PCNTL comes to mind -- obviously it's only useful in the CLI executable, but the Zend optimizer refuses to work with it at all, yet I still want to use it on the web server -- thus requiring seperate php.ini configurations.) I know that you can set PHPRC to another path before starting PHP up, either as CLI or from a web server, but it's quite a pain. There are also a few other work arounds, like the magic "#!" token at the beginning of shell scripts (which isn't at all portable), but I'm still thinking the best solution would be to split the php.ini files in two -- one for the web server SAPI and one for the CLI. Call them php.ini and php-cli.ini or something.

I would like to have different file name for cli config file by _default_ also. *1 for "php-cli.ini" -- Yasuo Ohgaki