3pm

How can I tell if my server has suExec and/or PHPsuExec?

__________________
Three Pillars Media
- Reseller - phantom dime99 -

decx

Create a phpinfo.php containing:

Upload it then acces it on your browser. If line 4 of the phpinfo shows CGI then your server is running PHPsuexec.

__________________
SH113

deastwood

it really is as simple as that 3pm, however as far as im aware pretty much every server surpass runs has it on.

__________________
Oxygen Solutions - Main Website
MoneyScience - Latest Project

3pm

Well, we had a reply from the admins that it wasn't on there so I asked when so I could have our clients start to prepare for it, but they went ahead and just did it. Yikes! So half the sites we host for are now down for the count.

__________________
Three Pillars Media
- Reseller - phantom dime99 -

deastwood

thats really weird i had thought it was on pretty much every server, have you managed to get everyone back up and sorted now?

__________________
Oxygen Solutions - Main Website
MoneyScience - Latest Project

cowboy

This is a result of the ownership for the PHP files. If support cannot get right to it to change them (because it takes a root login), you can easily do it yourself for your sites.

1. Download all your .php files (these are the only ones causing problems) to matching directories on your local machine.
2. Make a temp index.htm file that stops visitors with a "I'm working here message."
3. Delete all the php files you just downloaded, off your server.
4. Re-upload all the php files (except your index.php) via FTP. They will then have the proper permissions and ownership. (You cannot reset ownership or permissions by uploading over the original.)
5. Upload your index file and delete the temp index file.

Most FTP clients have a method of sorting files by type.

__________________
Where would you be if you were at the highest court in the land (US)?

decx

There's another major cause for broken scripts when switching from mod_php to PHPsuexec: PHP commands in .htaccess files. Since PHP is no longer running as part of Apache, it no longer understands any PHP commands placed in a .htaccess file. To get that problem solved just placed the PHP commands that were .htaccess files and place then in standalone php.ini files.

However note that with this method, php.ini files unlike .htaccess files, are not recursive. So if other subdirectories needs what you placed in the php.ini file you'll need to make a copy of it in those subdirectories also.

__________________
SH113