PHPsuexec - What You Need To Know

PHPsuexec works in much the same way that CGI (perl
scripts etc) with suexec does. All PHP scripts will be run under your
account user name UID/GID, rather than the user running the web server
which is the case when PHP is run as an apache module.

This
simply means that rules that apply to .cgi & .pl files on your
current server, now also apply to PHP files. The maximum permissions
permitted on directories and .PHP files are 755. Failing to have
permissions set to a MAXIMUM of 755 on PHP files and their installation
paths will result in a 500 internal server error, when attempting to
execute them.

What if a script needs 777 for directories or files!

This
is no longer required. You do not need to have directories or files set
to 777, even if your installation documents tell you that you do.
Permissions of 755 will work in the same way. Scripts owned by your
account user will be able to write to your files in the same way that
they can running under apache with 777 permissions.

If you have
PHP applications/scripts that have directories set to 777, (required to
write to them under PHP/apache module), they will need to be changed to
755. Also you will need to change ownerships of all files owned by user
"nobody" to the username for your account.

.htaccess

You can no longer manipulate the php.ini settings with .htaccess files.

If
you are using .htaccess with php_value entries within it, you will
receive a 500 internal server error when attempting to access the
scripts. This is because PHP is no longer running as an apache module
and apache will not know how to handle those directives any longer. All
PHP values should be removed from your .htaccess files to avoid this
issue. Placing a php.ini file in its place will solve this issue.

Read more
http://www.techentrance.com