Hi,
> yep, found in Configurable.pm
>
> >#####################################################################
> ># Load a particular class module and construct and return an instance
> ># return undef if it didnt work
> >sub load
> >{
> > my ($file, $class, @args) = @_;
> >
> > my $ret;
> > return unless eval("require $class") && ($ret = $class->new($file,
> > @args));
> > $ret->activate() unless $ret->isCheckingConfiguration();
> > return $ret;
> >}
>
> The object does no longer get activated if we are in check config
> mode, and the WARNING comes from findAndUse() later on.
confirmed. adjusting to older format:
$ret->activate();
the server passes the '-c' check with this config again.
so...whats the issue with having 'activate' in config checking mode? what does
this reversion expose us to? :-)
alan
_______________________________________________
radiator mailing list
[email protected]
http://www.open.com.au/mailman/listinfo/radiator
