Actually, based on what he wrote in his first message above, he's asking specifically about my Custom PHP mod script that a lot of people use which sets up and maintains separate PHP.INI configurations for each and every account independent of each other, supports templating, and keeps in sync with newly added or deleted accounts.
Solution
Yes its good idea to enable suphp on your server if you want to enable the custom php.ini file to each an every user as per there requirement so that every user can change the php values.
Note : On Suphp server php.ini file is working directory base due to that you need to add/copy php.ini in each directory where you want to change php values for your domain.
Yes its good idea to enable suphp on your server if you want to enable the custom php.ini file to each an every user as per there requirement so that every user can change the php values.
Note : On Suphp server php.ini file is working directory base due to that you need to add/copy php.ini in each directory where you want to change php values for your domain.
You may toggle or switch between preferences for SuExec and the PHP handlers (e.g., SuPHP) via your root WHM control panel at the following menu path:How can I enable suphp?!
WHM: Main >> Service Configuration >> Apache Configuration >> PHP and SuExec Configuration
Via the above page in WHM you can switch the PHP handler to SuPHP and ensure SuExec is enabled. If SuPHP is not listed in the drop-down menus for PHP then you will need to run EasyApache to enable support for SuPHP in Apache and PHP.
I recommend to reference the following documentation for more detailed information about the available PHP handlers:
ApachePHPRequestHandling < EasyApache3 < TWiki
It will help to know additional details:thanks but it's ok!
I did this many time ago!
bug php is not custom build!
1.) Are you needing to compile PHP using specific custom "configure" switches/options?
2.) Are there any specific requirements for a "custom build" of PHP? Please detail as verbosely as possible.
Regarding the above message from reporter and also my prior post as well ...thanks but it's ok!
I did this many time ago!
bug php is not custom build!
Reporter was originally running with a special configuration which setup automated custom PHP configurations with separate administrator only accessible PHP.INI files for each hosting account.
He made some unrelated changes to his server and broke a few system components that caused some wide problems throughout the entire server
and broke the custom PHP, Cpanel, and many other things. I am not going to embarrass him by telling everyone exactly what he did to his server.
However, I have already fixed the damage done, got everything working again in the system, and restored his original custom PHP configuration.
-Spiral
Last edited:
Solution
Simply check server is SuExec or not? | Linux Servers cPanel webhosting blog
As well as please post phpinfo URL in this thread so that we can check it for you.
Again I like to remind to Suphp server php.ini file is working directory base due to that you need to add/copy php.ini in each directory where you want to change php values for your domain.
As per your post it seems to be that you are totally confused with the SuExec concept.First you need to verify that your server is SuExec or not?Please read following thread carefully and try it.thanks but it's ok!
I did this many time ago!
bug php is not custom build!
Simply check server is SuExec or not? | Linux Servers cPanel webhosting blog
As well as please post phpinfo URL in this thread so that we can check it for you.
Again I like to remind to Suphp server php.ini file is working directory base due to that you need to add/copy php.ini in each directory where you want to change php values for your domain.