Doug MacEachern wrote:
On Fri, 13 Dec 2002, Stas Bekman wrote:Any special reason for calling modperl_init_vhost() after modperl_run() which already does that? This is in the 'perldo' command callback.
yes, because a <Perl> section or PerlLoadModule may have already triggered modperl_run, in which case modperl_run is a noop.
ai, this early startup drives me crazy.
and yes, the startup stuff is ugly, only because of early bootstrap required by <Perl> or PerlLoadModule. if you have ideas on howto fix that, great.the <Perl> and PerlLoadModule create a chicken and egg problem. May be we should start mod_perl early then kill it, then start again normally?
Because I've added an assert for something that wasn't caught before. Please run t/TEST -conf and try again. If it doesn't work please post your httpd.conf. Also make sure that Apache::Test is up-to-datecurrent cvs does not work for me, seems related to this area...
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
