Multiple php.ini instances - configuration tree errors (PHPIniDir)

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • forrie@gmail.com

    #1

    Multiple php.ini instances - configuration tree errors (PHPIniDir)

    We're running multiple vhosts in an apache-2.x configuration for which
    we would like to provide separate php.ini files (for different
    reasons).

    At the moment, we're unable to do this - the error I'm seeing is:

    Starting httpd: Syntax error on line 87 of
    /etc/httpd/conf/vhost.conf.admi n:
    Only first PHPINIDir directive honored per configuration tree -
    subsequent ones ignored
    [FAILED]

    So my question here is in a couple of parts. One, is it even possible
    to do what I'm trying to do... and what is a "configurat ion tree" -
    does that refer to the entire instance of the apache server itself. Is
    it possible to have more than one "configurat ion tree"s.


    Thanks!

  • Andy Hassall

    #2
    Re: Multiple php.ini instances - configuration tree errors (PHPIniDir)

    On 31 Oct 2006 12:43:06 -0800, "forrie@gmail.c om" <forrie@gmail.c omwrote:
    >We're running multiple vhosts in an apache-2.x configuration for which
    >we would like to provide separate php.ini files (for different
    >reasons).
    >
    >At the moment, we're unable to do this - the error I'm seeing is:
    >
    >Starting httpd: Syntax error on line 87 of
    >/etc/httpd/conf/vhost.conf.admi n:
    >Only first PHPINIDir directive honored per configuration tree -
    >subsequent ones ignored
    >[FAILED]
    >
    >So my question here is in a couple of parts. One, is it even possible
    >to do what I'm trying to do...
    Unless I've missed something, no, it's not.
    and what is a "configurat ion tree" -
    >does that refer to the entire instance of the apache server itself.
    Yes, looks that way.
    >Is it possible to have more than one "configurat ion tree"s.
    I don't think so. One Apache instance has one configuration tree; you'd have
    run a separate Apache instance per vhost, which would almost certainly be
    unmanageable.

    You can override some PHP settings per vhost in httpd.conf with php_flag and
    php_value, but that's not quite the same.

    --
    Andy Hassall :: andy@andyh.co.u k :: http://www.andyh.co.uk
    http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool

    Comment

    Working...