Description:
------------
The directory for reading additional ini files is hardcoded (declared as a constant). The base php.ini location is configurable, the additional ini file dir isn't.

Compare:
php_ini_opened_path
PHP_CONFIG_FILE_SCAN_DIR

Why they should BOTH be configurable:
What if I want to have multiple HTTP services with just a single set of binaries?

I may want to have serveral httpd.conf files, and have an Apache process started with different configuration files. In these files I could want to use the PHPINIDir directive. This works fine. The problem is that phpinfo() keeps whining about the "Scan this dir for additional .ini files" It's impossible to override this setting. Quite silly as we can easily have multiple php.ini files for different goals (cli, http, etc).

So first of all this should be configurable (and why not in php.ini?)
Systems must be able to have multiple "instances" of PHP running without actually having to compile separate binaries for different goals.

Reproduce code:
---------------
n/a

Expected result:
----------------
n/a

Actual result:
--------------
n/a