PHP 5.1.5 PHPSuexec and PHP.ini

Mysteerie

Well-Known Member
Dec 29, 2003
129
0
166
Has the problem been solved where the php.ini file couldn't be called from the local directory of the user?

I.e. if a user places a php.ini file in the directory, it doesn't work. If they place a phpinfo in the directory it shows that the it's alays calling on the default php.ini and not the local one.

I would test this myself, however I need to warn my members at least a good seventy two hours before applying any upgrades, so asking if anyone else can confirm if this problem has been solved. :)
 

Spiral

BANNED
Jun 24, 2005
2,020
8
193
FYI: phpSuExec is NOT supposed to read user's php.ini files!

When they first created phpSuExec in PHP v4 series,
the system would read local php.ini files for each user
but it was not a documented or supported feature and
we removed with the release of PHP v5 series.

Allowing users to write their own PHP.INI files is actually
a far greater security risk than not having phpSuExec
and is probably part of the reason that particular part
of phpSuExec was discontinued.

Also, phpSuExec is not needed at all if you are just simply
wanting to track programs that send out email. Exim itself
has a configuration option to log which scripts are sending
out email so even if they are sending email as 'nobody',
you still have logs showing which account actually sent the
mail and which script was used to send it.

Pretty much a no brainer!
 
Last edited:

cinusik

Active Member
Jul 31, 2003
38
1
158
cPanel Access Level
Root Administrator
It is not about just who is sending emails but how much is sending.
With phpsuexec the WHM config value set to 100 emails / hour let you send max 100 email per hour for each of your domain. Without phpsuexec this limit makes 100 emails per hour for all users on the server using php to send emails. So for me it is only one reason for using php with phpsuexec.
Anyway thanks for the info.
 

dreamwiz

Well-Known Member
Aug 28, 2003
93
0
156
Spiral said:
FYI: phpSuExec is NOT supposed to read user's php.ini files!

When they first created phpSuExec in PHP v4 series,
the system would read local php.ini files for each user
but it was not a documented or supported feature and
we removed with the release of PHP v5 series.
To be exact, per-directory php.ini works still with 5.0.5 but the feature has been removed from 5.1.x.