syslint
03-02-2011, 10:44 AM
I had faced bad suphp configurations in a number of da servers for our support clients, with multiple useless php and its issues. So I had to write this article. It is easy to build an suphp server without a number of php instances and to build a clean system , with the following features,
This php will be installed under /usr/local/ instead of /usr/local/php5
There is no conflict with multiple server php binaries
The php ini path is /usr/local/lib/php.ini
This will help to set correct path for php scripts or cron jobs without modifying the client files
No modification for default template , just use custom.
Use server mysql for php-mysql client instead of bundled php , this will avoid client API conflict
Give simplicity for new directadmin users
Easy to implement
The article is located on here (http://syslint.com/syslint/howto-directadminapache-2-2php5suphpsuexec-perfect-setup/)
If you need an autoinstaller script for it download from here (http://files.syslint.com/da/syslint_apachebuild_suphp_5.2.sh)
This php will be installed under /usr/local/ instead of /usr/local/php5
There is no conflict with multiple server php binaries
The php ini path is /usr/local/lib/php.ini
This will help to set correct path for php scripts or cron jobs without modifying the client files
No modification for default template , just use custom.
Use server mysql for php-mysql client instead of bundled php , this will avoid client API conflict
Give simplicity for new directadmin users
Easy to implement
The article is located on here (http://syslint.com/syslint/howto-directadminapache-2-2php5suphpsuexec-perfect-setup/)
If you need an autoinstaller script for it download from here (http://files.syslint.com/da/syslint_apachebuild_suphp_5.2.sh)