A few years ago I installed Apache 2.2x and PHP 5.3.1 on a Linux server I maintain. I used .tar.gz's and built them as instructed (instead of rpms and what-have-you). And all was fine.
Today I need to install this which seems like a PHP library. I went through all the steps up to make install, and I found ibm_db2.so in $PHP_HOME/lib/extensions/somecomplicatedname/ibm_db2.so
.
The great catch is the last step is to configure file php.ini, but there aren't any php.ini files on my system. Horror of horrors. PHP works fine, except of course for this newfangled ibm_db2 thingamajig that I want to use so somebody can use a GUI to tinker with DB2. (I tried a small PHP script which fails and indicates that the ibm_db2 functions are not available.)
I have to deal with PHP once every few years, so please enlighten me at a very basic level about what I could do to enable web-based GUI access to DB2.
locate php.ini
will tell you in mere moments where the file is on your system.
On the command line execute:
php --ini
You will get something like:
Configuration File (php.ini) Path: /etc/php5/cli
Loaded Configuration File: /etc/php5/cli/php.ini
Scan for additional .ini files in: /etc/php5/cli/conf.d
Additional .ini files parsed: /etc/php5/cli/conf.d/curl.ini,
/etc/php5/cli/conf.d/pdo.ini,
/etc/php5/cli/conf.d/pdo_sqlite.ini,
/etc/php5/cli/conf.d/sqlite.ini,
/etc/php5/cli/conf.d/sqlite3.ini,
/etc/php5/cli/conf.d/xdebug.ini,
/etc/php5/cli/conf.d/xsl.ini
That's from my local dev-machine. However, the second line is the interesting one. If there is nothing mentioned, have a look at the first one. That is the path, where PHP looks for the php.ini
file.
You can grep the same information using phpinfo() in a script and call it with a browser. It’s mentioned in the first block of the output. php -i
does the same for the command line, but it’s quite uncomfortable.
The best way to find this is:
Create a PHP (.php) file and add the following code:
<?php phpinfo(); ?>
and open it in a browser. It will show the file which is actually being read!
Updates by the OP:
The previously accepted answer is likely to be faster and more convenient for you, but it is not always correct. See comments on that answer. Please also note the more convenient alternative mentioned in this answer.
<?php phpinfo(); ?>
php -r \@phpinfo\(\)\;
works for me php -r \@phpinfo\(\)\; | grep 'PHP Version' -m 1
to pull specific info
<?php echo php_ini_loaded_file(); ?>
This works for me:
php -i | grep 'php.ini'
You should see something like:
Loaded Configuration File => /usr/local/lib/php.ini
P.S.
To get only the php.ini path, use:
php -i | grep /.+/php.ini -oE
php.ini
, which is exactly the problem: If there is none, you still don't know where to look at, or where to place a new one.
Configuration File (php.ini) Path => /usr/lib
, but running <?php phpinfo(); ?>
gives me Loaded Configuration File: /etc/php.ini
. So, phpinfo()
was more reliable in my case.
php -i | grep 'php.ini'
from apache? (script.php)
In a command window, type
php --ini
It will show you the path something like:
Configuration File (php.ini) Path: /usr/local/lib
Loaded Configuration File: /usr/local/lib/php.ini
If the above command does not work then use this:
echo phpinfo();
Use the following command to find the php.ini
file path on Linux.
locate php.ini
Output:
/etc/php.ini
/etc/php.ini.rpmnew
/usr/share/doc/php-common-5.4.45/php.ini-development
/usr/share/doc/php-common-5.4.45/php.ini-production
Or try this other way:
php --ini
It shows the path result.
php -i | grep 'php.ini'
, because it finds any php.ini and doesn’t tell you which one your PHP installation uses. Also, it may give wrong results when the locate
DB is not up to date.
locate
is not installed by default on Ubuntu MATE 20.04 (Focal Fossa).
This command should help you to find it
php -r "phpinfo();" | grep php.ini
PHP comes with two native functions to show which configuration file is loaded:
php_ini_loaded_file returns the loaded .ini file
php_ini_scanned_files returns a list of .ini files parsed from the additional ini directory
Depending on your setup, Apache and CLI might use different .ini files. Here are the two solutions:
Apache:
Just add the following in a PHP (.php) file and open it in your browser:
print php_ini_loaded_file();
print_r(php_ini_scanned_files());
CLI:
Copy-paste in your terminal:
php -r 'print php_ini_loaded_file(); print_r(php_ini_scanned_files());'
php_ini_loaded_file
may not always be available.
php_ini_loaded_file
say php version >= 5.2.4
phpinfo();
will tell you its location, or from the command line
php -i
Run this in the command line:
php -r "echo php_ini_loaded_file().PHP_EOL;"
Try one of these solutions
In your terminal, type find / -name "php.ini" In your terminal, type php -i | grep php.ini. It should show the file path as "Configuration File (php.ini) Path => /etc" If you can access one of your PHP files, open it in a editor (Notepad) and insert phpinfo(); after
find / -name php.ini
Hey... it worked for me!
php --ini
works, but this is just another option :) There is usually a /etc/php5/cli/php.ini
/etc/php5/apache2/php.ini
/etc/php5/cgi/php.ini
and usually which one you want is pretty obvious. (cli, apache, cgi)
You can get more information about your configuration files using something like:
$ -> php -i | ack config # Use fgrep -i if you don't have ack
Configure Command => './configure' ...
Loaded Configuration File => /path/to/php.ini
For SAPI: php-fpm
There isn't any need to create a php.info file (it is not a good policy to leave it for the world to read anyway). On the command line:
php-fpm -i | more
Somewhere in its output, it will show this line:
Configuration File (php.ini) Path => /etc
Here is a more complete explanation: How to Figure out Your PHP Configuration Parameters without info.php
according to this answer, as of PHP 7 the regular php.ini file was removed and added with php.ini-production
and php.ini-devlopment
.
so instead of php.ini which does not exist in my case (I've installed php 8.1), use php.ini-production
and it's located in php installation folder (something like: C:\PHP-8.1.5
) and create a file and name it php.ini
and then copy contents of php.ini-production
in this new php.ini
.
Success story sharing
.php
file. By the way, if you comment on the question then I get notified and I can fix the problem sooner.phpinfo.php
-like file. With FPM you can at least usephp5-fpm -i | grep '\.ini'
. Usually you use this two or three times and at the end of the day you know where the files are ;)