suphp to mod_php

[neverhood]

Hi guys, hope you`ll find some time to help. I`m having the following problem:

there`s a vps that holds around 200 sites ( very light ones ) , apache uses suphp, now we decided we might need to recompile it to use mod_php instead. As far as i understand( i fear i dont have a possibility to test it now) the changes in "options" file will only affect new vhosts ( the way they`ll be recorded).

I would be really happy to see any suggestions/theory/advices , because atm i fear i have no idea where do i need to start at.

Thanks!

 

[tillo]

"Do not fix what is not broken". Is there a particular reason to change the way PHP is called?
If you are looking for the [very small] gain in performance, I strongly suggest you reconsider: mod_php is not secure enough for a shared hosting service.

There are many threads in this forum about the advantages of using PHP as CGI (through suphp, suexec, FastCGI or any other method) and how to migrate from mod_php, but I never saw a good reason to do the inverse. If you do, I'd like to know it.