I moved from apache 1.3 and php 5.2.5 with eaccelerator to
apache 2.2 with php 5.2.5 and suphp
With apache 1.3 php 5.2.5 and eaccelerator my system load was rarely higher than 1.
With apache 2.2/suphp my server load medium value was 6 (yes 6) and all the days the server was crashing ..
I returned to apache dso with eaccelerator without suphp .. All works excellent now such as before ..
Especially disabling suphp the %system usage reported by "sar" passed from a medium of 30% to only 7% !!
If you have an old slow server stay FAR from suphp , it will mutiple your server load !!.
The solution to solve all the problems with php , python , perl ... is chorooting users .
Unluckly whm looks always at the easy way (phpsuxec , suphp...) but these solutions
are not good and causes only problems to us . I truly hope WHM will decide a day (version 12?)
to chroot users , so will not have more worries about php safe mode , suphp , openbase dir , suexec ..... and countless problems with python
,ruby on rails , perl , php ...
apache 2.2 with php 5.2.5 and suphp
With apache 1.3 php 5.2.5 and eaccelerator my system load was rarely higher than 1.
With apache 2.2/suphp my server load medium value was 6 (yes 6) and all the days the server was crashing ..
I returned to apache dso with eaccelerator without suphp .. All works excellent now such as before ..
Especially disabling suphp the %system usage reported by "sar" passed from a medium of 30% to only 7% !!
If you have an old slow server stay FAR from suphp , it will mutiple your server load !!.
The solution to solve all the problems with php , python , perl ... is chorooting users .
Unluckly whm looks always at the easy way (phpsuxec , suphp...) but these solutions
are not good and causes only problems to us . I truly hope WHM will decide a day (version 12?)
to chroot users , so will not have more worries about php safe mode , suphp , openbase dir , suexec ..... and countless problems with python
,ruby on rails , perl , php ...
Last edited: