Looking for the pro's and con's of implementing PHP-Suexec on live servers with lots of hosts and resellers.

Really just looking to hear what others experience has been and why they did or did not implement it.

regards

you maybe have to modify the code of one modules about apache.

pro's:
- running on the users uid / gid
- easily tracking spamming users (cause mail isn't send by apache)

Con's:
- Script debug info is shown in the error.log and not on the screen
- You need to patch APACHE yourself (patches are available though)
- Apache authentication with PHP won't work anylonger.
- You need another patch to specify a PHP.INI opn a virtualhost bases.


Aftherall I'm glad I switched cause of the fact users can't mess with my system anylonger :).

PHPsuexec should also eat up more resources. But that's not a big price with the speeds nowadays.

Why should it use more resources? I don't see why, cause it is a static binary that is only included when requesting a PHP file and isn't included in every apache instance as module.

It will be slower because its not built into apache.

But on the other hand Apache won't use the binary if not nesecary and with mod_php it is always included......

Could this thread (http://www.webhostingtalk.com/showthread.php?s=&threadid=160495) also be one of the Cons?

your quotatool will be more reliable?

You mean pro's ;)

Yes I do

well .. is it? I'am spending hours here (1:31 at night in the Netherlands) to find an answer for THIS TOPIC (http://www.webhostingtalk.com/showthread.php?s=&threadid=160495)

help is very much appreciated ...

I'm also Dutch ;). So don't complain :). If you need help contact me by email ( elsten A-T starhost DoT nl ).

Well maybe I do, but first a little sleep here. Maybe I just contact you by phone tommorow :-)
After taking a look at your good looking site :agree: