CGI Suexec off - HELP !

[jeroman8]

After running easyapache all CGI is started to have issues and I think suexec is not running.

Anyway - before there was a speciel suexec page for cgi/perl in WHM.
Now the only suexec link there is, is inlcuded in the php config page.

I wanna have suexec ON for cgi scripts.
I wanna have suexec OFF for php scripts.

So my question:

The suexec option on the "Configure PHP and SuExec" page - is it for CGI och for both cgi and php or only php ??

 

[cPanelDavidG]

After running easyapache all CGI is started to have issues and I think suexec is not running.

Anyway - before there was a speciel suexec page for cgi/perl in WHM.
Now the only suexec link there is, is inlcuded in the php config page.

I wanna have suexec ON for cgi scripts.
I wanna have suexec OFF for php scripts.

So my question:

The suexec option on the "Configure PHP and SuExec" page - is it for CGI och for both cgi and php or only php ??

SuExec is only for Perl. If you want to have PHP scripts run as user, use SuPHP. If you selected SuPHP during the EA3 build process, you should see it in the drop-down for PHP handler.

PhpSuExec is no longer available as of EA3, SuPHP should be used instead.

 

[myweb]

SuExec is only for Perl. If you want to have PHP scripts run as user, use SuPHP. If you selected SuPHP during the EA3 build process, you should see it in the drop-down for PHP handler.

PhpSuExec is no longer available as of EA3, SuPHP should be used instead.

I think this is very confusing. If I dont select suPHP in EA3, I dont even see the dropdown in the page so I thought that the suExec section in that page actually meant PhpSuExec. I think the page should at least display that SuPHP is disabled and should be titled like "Configure Perl Suexec and PHP" to avoid confusion.

 

[cPanelDavidG]

I think this is very confusing. If I dont select suPHP in EA3, I dont even see the dropdown in the page so I thought that the suExec section in that page actually meant PhpSuExec. I think the page should at least display that SuPHP is disabled and should be titled like "Configure Perl Suexec and PHP" to avoid confusion.

I see an internal case recommending this cosmetic change. (case 3965)

(Removed, see Kenneth's explanation for SuExec applying to all CGI apps)

I understand the confusion as everything else on that page is only for PHP, one would naturally assume if they are quickly looking through things that this was a PHP-specific option as well.

 

[cPanelKenneth]

suExec is for any application run via CGI, regardless of programming language. suExec is suExec as provided by the Apache project. PHPsuExec was a patch we used to provide, a patch for suExec. As such, there was not a separate PHPSuExec binary, only the suexec binary.

To use PHP, in particular, with suExec, one must set the handler to CGI in the 'Configure PHP and suExec' editor/page and enable suExec.

 

[boatdesign]

Thanks Kenneth. Just ran into this issue myself tonight as well, and this thread solved it.
WHM verbage is very confusing to me in that if you click "Configure PHP and SuExec" you are greeted with a statement:

This tool allows you to select how Apache will deliver PHP content

which to me, implied different than

suExec is for any application run via CGI