Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:php:per-user-php-ini [2018/07/02 11:17]
qtwrk [Notes]
+++ litespeed_wiki:php:per-user-php-ini [2018/09/14 16:03]
Michael Alegre [Notes]
@@ Line 107: / Line 107: @@
 ===== Notes =====
   * **PHP suEXEC MUST BE ENABLED IN LSWS.**
-  * Make sure the php.ini file is readable by the suEXEC user.
+  * Make sure the php.ini file is readable by the **Run As User** user.
   * Option 3 can be used along with options 1, 2, or 4 without conflicts. However, this should rarely be needed.
   * Option 4 takes precedence over options 1 and 2 should they be used at the same time.
   * Changes in the php.ini will not be picked up until new PHP process starts. The php.ini is read for the first time when a PHP process starts.
-  * Per-user php.ini files are not compatible with [[http://www.litespeedtech.com/products/litespeed-sapi/php/suexec-daemon-mode|suEXEC Daemon mode]]. Our [[http://www.litespeedtech.com/products/litespeed-sapi/php/guide-to-suexec-setups|two other PHP suEXEC setups]] both support per-user php.ini.
+  * Per-user php.ini files are not compatible with [[http://www.litespeedtech.com/products/litespeed-sapi/php/suexec-daemon-mode|Daemon mode]]. Our [[http://www.litespeedtech.com/products/litespeed-sapi/php/guide-to-suexec-setups|two other PHP process modes]] both support per-user php.ini.
   * For native LSWS installs, these variables ($VH_ROOT, $VH_NAME, $VH_USER, etc.) need to be inside of a Virtual Host External App Environment Section, and not inside the general Server External App Environment Section. This is because the variables are expanded on start up, so the VH_* variables cannot be expanded during server level configurations.
 ===== Troubleshoot =====
-  * Some PHP extension missing after loaded with per user php.ini, for example **Your PHP installation appears to be missing the MySQL extension which is required by WordPress.**
+Some PHP extensions are missing after being loaded with per user ''php.ini'', for example
+<code>Your PHP installation appears to be missing the MySQL extension which is required by WordPress.</code>
-This is because once custom php.ini is loaded , the default php.ini will be ignored , therefore extensions will not be loaded.
+This is because once custom php.ini is loaded, the default php.ini will be ignored. Therefore, extensions will not be loaded.
-To resolve this problem , the easier way to go is copy the content of default php.ini into custom php.ini by following command:
+The easiest way to resolve this problem is to copy the contents of the default php.ini into the custom php.ini by the following command:
 <code>cat /opt/cpanel/ea-phpXX/root/etc/php.ini /opt/cpanel/ea-phpXX/root/etc/php.d/*.ini > /path/to/php.ini</code>
-Please replace ''ea-phpXX'' and ''/path/to/php.ini'' to corresponding version and path.
+Please replace ''ea-phpXX'' and ''/path/to/php.ini'' with the appropriate version and path.
-Verify the php.ini content and restart lsws if necessary, as change in php.ini will not take effect until new PHP process starts. The php.ini is read for the first time when a PHP process starts.
+Verify the php.ini content and restart LSWS if necessary, as a change in php.ini will not take effect until a new PHP process starts. The php.ini is read for the first time when a PHP process starts.