The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

PHP 5.1.5 PHPSuexec and PHP.ini

Discussion in 'General Discussion' started by Mysteerie, Aug 19, 2006.

  1. Mysteerie

    Mysteerie Well-Known Member

    Joined:
    Dec 29, 2003
    Messages:
    129
    Likes Received:
    0
    Trophy Points:
    16
    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. :)
     
  2. cinusik

    cinusik Active Member

    Joined:
    Jul 31, 2003
    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    cPanel Access Level:
    Root Administrator
    I'll try and I'll let you know ;)
    I'm waiting for thisone from few months.
     
  3. cinusik

    cinusik Active Member

    Joined:
    Jul 31, 2003
    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    cPanel Access Level:
    Root Administrator
    Bad news :( Phpsuexec still not reading users php.ini's.
     
  4. Spiral

    Spiral BANNED

    Joined:
    Jun 24, 2005
    Messages:
    2,023
    Likes Received:
    7
    Trophy Points:
    0
    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!
     
    #4 Spiral, Aug 19, 2006
    Last edited: Aug 19, 2006
  5. cinusik

    cinusik Active Member

    Joined:
    Jul 31, 2003
    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    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.
     
  6. dreamwiz

    dreamwiz Well-Known Member

    Joined:
    Aug 28, 2003
    Messages:
    93
    Likes Received:
    0
    Trophy Points:
    6
    To be exact, per-directory php.ini works still with 5.0.5 but the feature has been removed from 5.1.x.
     
Loading...

Share This Page