Aaron Bannert wrote: > > On Mon, Apr 22, 2002 at 04:01:25PM -0400, Jim Jagielski wrote: > > Right now, we assume that each successive use of PHPINIDir is > > due to its inclusion in a <VirtualHost container>. I wonder if > > that's overly restrictive... Should we allow successive uses and > > just honor the last one? > > Since the PHPINIDir is supposed to be a per-server config directive, > it should only occur in the global config or in a vhost config. > Ultimately I think this directive should be able to apply per-vhost, > but at the moment that isn't possible. The problem is that we can only > initialize with one php.ini, but at module startup time (for us this is > post_config) we don't know which vhost we'd like to serve. > > I think the problem will become more apparent as the perchild MPM > becomes more mature, so for now I just kept it as simple as possible > and disallowed attempts at per-vhost configs. >
Guess I wasn't clear :) If httpd.conf includes: PHPINIDir "foo" . . . PHPINIDir "bar" The latter isn't allowed, and assumes a Vhost reason. I wonder if, instead, we should allow the 2nd to override the 1st override, as it were :) Agreed that for perchild something better will be needed :) -- =========================================================================== Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
