httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@gmail.com>
Subject Re: [PATCH/heads up] mod_fcgid: checking for global-only directives in a vhost
Date Wed, 16 Sep 2009 16:42:34 GMT
On Wed, Sep 16, 2009 at 11:42 AM, Rainer Jung <rainer.jung@kippdata.de>wrote:

> On 16.09.2009 17:18, Jeff Trawick wrote:
> > This has the potential for breaking existing configs by forcing the
> > admin to remove some ignored directives they've coded in a vhost.
> >
> > The affected directives are BusyScanInterval,
> > DefaultMaxClassProcessCount, DefaultMinProcessCount, ErrorScanInterval,
> > IdleScanInterval, IdleTimeout, MaxProcessCount, PHP_Fix_Pathinfo_Enable,
> > ProcessLifetime, SharedmemPath, SocketPath, SpawnScore,
> > SpawnScoreUpLimit, TerminationScore, TimeScore, and ZombieScanInterval.
> >
> > I suppose that a couple of these might have seemed to the administrator
> > to be more flexible than global-only, though it wouldn't have changed
> > the behavior when they added any of these to a vhost.
>
> Does it make sense to correctly merge some of them? I didn't check right
> now. Maybe some things are singletons, like the scanners, but others
> moght make sense per vhost, like e.g. the IdleTimeout or the scores.
> Consider e.g. when various vhosts use different wrappers.
>

In the long term, maybe a few of them should support vhost-specific settings
(PHP_Fix_Pathinfo_Enable, IdleTimeout, or ProcessLifetime).  We'll see what
people ask for (or who jumps in to implement ;) ).

At the moment I'm more interested in fixing the settings that pretend to be
merged and/or aren't picked up from the proper vhost.

Mime
View raw message