Check which php ini is being used

Where is php.ini? Find the Correct PHP Configuration File

The php.ini file is a configuration file used by PHP to specify settings for your web server, such as file upload size, error reporting, and memory usage. However, the location of the php.ini file can vary depending on your server setup and operating system.

In this tutorial, we will explore a few methods to help you locate the correct php.ini file on your web server.

Method 1: Use phpinfo() function

The phpinfo() function displays detailed information about your PHP configuration, including the location of your php.ini file. To use this function, follow these steps:

1. Create a new PHP file on your web server. You can name it anything you like, but for this tutorial, we will name it phpinfo.php.
2. Open the phpinfo.php file in a text editor and add the following code:

You should see a page with detailed information about your PHP configuration. Look for the “Loaded Configuration File” section, which should contain the full path to your php.ini file.

Method 2: Use the command line

If you have access to the command line, you can use the `php —ini` command to find the location of the php.ini file. Follow these steps:

1. Log in to your web server using SSH or another terminal application.
2. Type the following command and press Enter:

This command will display a list of all the php.ini files that are currently being used, as well as their locations.

Method 3: Check default locations

Depending on your operating system and server configuration, the php.ini file may be located in one of the default locations. Here are some common default locations:

On Linux:

On Windows:

You can try searching for the php.ini file in these locations using your FTP or file manager.

If none of these methods work, you can contact your web hosting provider or system administrator for assistance in locating the php.ini file on your server.

Conclusion

The php.ini file is an essential configuration file for PHP. By following the methods outlined in this tutorial, you should be able to locate the correct php.ini file on your web server. Remember, the location of the php.ini file can vary depending on your server setup and operating system, so it’s important to double-check the location before making any changes to the file.

Источник

Identifying the PHP.ini File in Use

To handle any errors triggered in PHP, set_error_handler can be used with a callback function. However, this only applies to non-fatal errors since fatal errors cannot be handled once the PHP engine fails, for example, with syntax errors. If you want to handle fatal errors, you need to define a shutdown_function, as explained in «How do I catch a PHP Fatal Error». Another solution is to use error_reporting without a parameter to retrieve the current error reporting status.

Why is the wrong php.ini being used?

My host is utilizing suPHP which, along with phpSuExec, does not allow subdirectories to inherit configuration from php.ini files. Subdirectories will instead use the default php.ini.

This website talks about the PHP include path and its usage.

• To ensure proper script functionality, it is necessary to locate a specific php.ini file in every directory that contains script loading.
• Employing a suPHP_ConfigPath /home/username/public_html/ directive within the .htaccess file can direct to the folder holding your personalized php.ini file. This will apply to all subdirectories without an existing php.ini file.

This issue pertains to your web hosting provider and is not solely related to PHP. In case you have developed a custom system, it is essential to identify the Apache extension utilized for executing PHP files.

As an illustration, in my work system, I utilize SUPHP as a script engine, enabling me to specify the location of a particular PHP.ini file.

How can I know which ‘php.ini’ file is used?, Most PHP installations would come with a php.ini file for Apache and another for CLI. To know which configuration file is used for the console commands, use. php -i | grep «Configuration File». To know which configuration file is used for the web processes, follow these steps. Create an info file (preferably …

Determining the run-time source of the PHP.INI values that were used to evaluate the pre-processing?

After encountering difficulties while installing apd on a new distribution, which is an outdated library, I can now proudly announce that I have a fully operational instance with the help of «pecl runkit».

To install runkit , PECL can be used.

Append the subsequent code to your php.ini file.

 extension=runkit.so runkit.internal_override=1 

It should be noted that error_reporting can be defined in various ways, such as through the use of error_reporting() function or ini_set . Therefore, it is important to be mindful of each function. Initially, we duplicate the old ini_set with runkit_function_copy , and subsequently modify it with runkit_function_redefine .

To obtain the file and line number of the call, I utilize debug_bactrace(1) .

To capture both non-lethal and lethal errors, a combination of set_error_handler and register_shutdown_function must be employed.

Upon encountering an error, the code will display the location of the call to ini_set along with the corresponding filename and line number.

A type 2 error occurred on line 47 of file /var/www/html/test.php due to division by zero.

• The order in which error_reporting was defined is as follows:
• /var/www/html/test.php, line 16, value: 0
• /var/www/html/test.php, line 17, value: 2
• /var/www/html/test.php, line 18, value: 1
• /var/www/html/test.php, line 19, value: 32767

"; foreach ($iniset as $key=>$val) < echo "
• $key was defined here (in order):
  "; foreach ($val as $def) < echo "
  • , line , value: ".array_pop($def['args']).""; > echo "

  Previous post:

  Utilizing the ini_get_all() function allows for retrieval of the values for both local and global configuration options.

  By enabling the $details parameter, you can obtain both local and global values.

  To obtain the value of specific options, you may use the ini_get() function to retrieve the runtime value or the get_cfg_var() function to access the global php.ini value.

  $global_value=get_cfg_var("error_reporting"); $local_value=ini_get("error_reporting"); echo "Error reporting (Local value: $local_value, global value: $global_value)\n" 

  To observe the outcomes during an error, it is necessary to capture the errors.

  To handle errors that are not fatal, the function set_error_handler() can be utilized.

  To handle PHP Fatal Errors, it's essential to specify a shutdown_function(). Check out the guide on How do I catch a PHP Fatal Error.

  By not specifying parameters, error_reporting() allows you to retrieve the current error reporting status. In order to check for specific functionalities, use error_reporting() & (E_STRICT | E_COMPILE_WARNING) to test whether E_STRICT and E_COMPILE_WARNING are enabled.

  In case you desire detailed information regarding phpinfo() , you may obtain it by capturing the output of phpinfo and saving it, along with HTML formatting, to the error log or any other location.

  ob_start(); phpinfo(); error_log(ob_get_clean()); 

  Keep in mind that the phpinfo() will only be logged and won't be displayed in the response.

  You could potentially improve your stack trace by implementing xdebug. It may be worth considering.

  As the extent of your inquiry is ambiguous, I will share my knowledge about PHP's error handling and leave it to you to make sense of it.

  Detecting code changing php.ini settings

  Your question implies that your code is altering default settings, causing the occurrence of error types that should have been deactivated.

  To avoid altering the settings in the code, one can utilize a tool called PHP Code Sniffer, which comes with a customizable rule known as "ForbiddenFunction". This rule can be used to identify calls to various functions, including but not limited to ini_set and error_reporting .

  To address the presence of these functions, it's necessary to scan the code for their calls and examine the purpose behind them. Merely eliminating them may not be the optimal solution, since modifying error settings could have a rationale. It's possible that the code erroneously reverts the value to its initial state.

  Getting at the current values of settings at runtime

  By utilizing register_tick_function, you have the ability to set up a callback function that will execute during regular code execution. This function will be triggered after a certain number of "ticks", which refers to the number of low level statements executed. Keep in mind that implementing this feature may impact the runtime of the script, as the registered function will execute frequently.

  The function has the ability to examine any desired element and respond accordingly to any modifications.

  Getting at the current values in case of errors/exceptions

  One can set up their own handler for errors and exceptions by making use of the set_error_handler function. The function will receive a callback as input, which will provide all the details of the error that was triggered (excluding fatal errors). If PHP engine fails due to syntax errors, for instance, no further calls can be made.

  bool handler ( int $errno , string $errstr [, string $errfile [, int $errline [, array $errcontext ]]] ) 

  Irrespective of the chosen setting of error_reporting() , the function will be executed. However, the function can also read the setting and avoid calls with disabled errors. For instance, it can read the global php.ini setting or ignore all other errors. Alternatively, it can report these errors in a distinct log file. If the function returns false , the regular error handling will be triggered. On the other hand, if it returns true , the program will proceed as though no error occurred.

  The $GLOBALS array allows for the retrieval of global variables.

  Uncaught exceptions can be managed through a registered callback using set_exception_handler. The callback receives the exception object containing details such as message and stack trace.

  And now?

  Consider addressing the code issues to prevent potential breakage during PHP updates. It's difficult to offer specific advice without additional details, but it's important to identify and resolve any underlying coding problems. Ignoring these issues may provide temporary relief, but it's likely to cause more significant problems down the line. Rather than simply reducing the error log footprint, prioritize finding and fixing the root cause of the errors.

  How can I find the php.ini file used by the command line?, $ strace -o strace.log php --version $ grep php.ini strace.log Strace digs out kernel (system) calls that your program makes and dumps the output into the file specified by -o. It's easy to use grep to search for occurrences of file php.ini in this log. It's pretty obvious looking at the following typical response to see …

  Laravel artisan serve, reload php.ini file

  Consider the following suggestions to troubleshoot the issue: Firstly, ensure that there is no duplication of the line that sets the limit in PHP.ini. Secondly, check if there are multiple files of PHP.ini that are loaded. Thirdly, verify whether the PHP.ini used by your command-line differs from the one used by your webserver. Lastly, conduct a search using grep -r in all your configuration files to locate where the 256 is set.

  Php.ini: which one?, You can check that running php --ini from the command-line. fpm/php.ini will be used when PHP is run as FPM -- which is the case with an nginx installation. And you can check that calling phpinfo () from a php page served by your webserver. cgi/php.ini, in your situation, will most likely not be used. Usage exampleln -s /etc/php5/php.ini php.iniFeedback

  Источник

  Читайте также:  Количество чисел больших предыдущего python