php creates files with owner 'nobody'

[guysmiley]

Greetings,

Using Joomla, when I create a folder, it has owner=nobody. I presume since php is being invoked to make this folder, it is php assigning 'nobody' as the owner.

Why would php be doing this?

[cPanelDavidG]

Greetings,

Using Joomla, when I create a folder, it has owner=nobody. I presume since php is being invoked to make this folder, it is php assigning 'nobody' as the owner.

Why would php be doing this?

This is the default behavior of PHP.

If you prefer that scripts run as the user and files created by these scripts be owned by the user, I recommend running SuPHP (or if you're running PHP as CGI, SuExec).

[mambovince]

I recommend running SuPHP (or if you're running PHP as CGI, SuExec).

I am running PHP as CGI with SuExec on one server.
Noticed load shows high now for PHP5.

- Would SuPHP lower the load?

- Any 'gotchas' to look out for if I change to SuPHP?

Many thanks,

- Vince

[mambovince]

I am running PHP as CGI with SuExec on one server.
Noticed load shows high now for PHP5.

- Would SuPHP lower the load?

- Any 'gotchas' to look out for if I change to SuPHP?

Anyone?
Also, would you run SuPHP if you're running PHP as CGI or Apache mod, with/without SuExec?

Many thanks,

- Vince

[cPanelDavidG]

Anyone?
Also, would you run SuPHP if you're running PHP as CGI or Apache mod, with/without SuExec?

Many thanks,

- Vince

I am unsure about loads, but SuPHP is used when PHP is not running as CGI/FastCGI. When PHP is running as CGI/FastCGI, SuExec is used instead as that targets CGI apps.

You wont have an instance where a single PHP installation is running under SuExec and SuPHP simultaneously.

[mambovince]

Thanks David,
So I cannot run SuPHP on this server then, because it has concurrent PHP4/5 with PHP4 running as Apache MOD?

Lastly, any 'gotchas' to look out for if I change to SuPHP?
'm worried about existing client sites that need 777 permissions on some directories.

Thanks again,

- Vince

[cPanelDavidG]

Thanks David,
So I cannot run SuPHP on this server then, because it has concurrent PHP4/5 with PHP4 running as Apache MOD?

I believe you misunderstood my statement. If you run PHP as an Apache module, you can use SuPHP. If you run PHP as any form of CGI, you cannot use SuPHP, and must use SuExec instead as SuExec handles this functionality for CGI applications.

Lastly, any 'gotchas' to look out for if I change to SuPHP?
'm worried about existing client sites that need 777 permissions on some directories.

Thanks again,

- Vince

SuPHP does not permit excessive permissions such as 777 as they are not required in a SuPHP environment. Scripts with 777 permissions or including files with 777 permissions will generate a HTTP 500 error once SuPHP is running.

Note, any applications that rely on 777 permissions typically mean that whatever user PHP is running as must be able to read, write and execute the file. In a mod_PHP environment, xx7 permissions are required as PHP is running as user nobody. However, when SuPHP is running, you can use 755 permissions or lower without issue since PHP is now running as that individual user.

Most modern PHP scripts will easily accommodate SuPHP setups. Generally it's only scripts that are unaware of common contemporary PHP security practices that blindly insist on and inappropriately enforce 777 permissions.

[mambovince]

Thanks for the comprehensive reply, I'm sure it will help others as well as myself.

Lastly, if I use EasyApache to recompile with SuPHP, does it also check and change all directories and files with 777 and change them to 755?

If not, is there another script to do this?

Best wishes,

- Vince

[cPanelDavidG]

Here's a related thread that answers that question and may answer additional questions you may think of:

http://forums.cpanel.net/showthread.php?t=78985