On Wed, Sep 16, 2009 at 11:42 AM, Rainer Jung 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,
> > De
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, ErrorScanInter
Jeff Trawick wrote:
>
> Please object now if you want to allow affected existing configurations
> to continue to work. We can probably change the hard failure to a warning.
As this is a beta, let's just break the config, we should put something very
clear in README about this.
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
