Any special reason for calling modperl_init_vhost() after modperl_run() which
already does that? This is in the 'perldo' command callback.
modperl_run -> modperl_hook_init -> modperl_init -> modperl_init_vhost ->
modperl_init_vhost
Index: src/modules/perl/modperl_cmd.c
===================================================================
RCS file: /home/cvs/modperl-2.0/src/modules/perl/modperl_cmd.c,v
retrieving revision 1.33
diff -u -r1.33 modperl_cmd.c
--- src/modules/perl/modperl_cmd.c 7 Oct 2002 15:45:52 -0000 1.33
+++ src/modules/perl/modperl_cmd.c 11 Dec 2002 14:29:58 -0000
@@ -337,10 +337,6 @@
/* we must init earlier than normal */
modperl_run(p, s);
- if (modperl_init_vhost(s, p, NULL) != OK) {
- return "init mod_perl vhost failed";
- }
-
#ifdef USE_ITHREADS
/* XXX: .htaccess support cannot use this perl with threaded MPMs */
aTHX = scfg->mip->parent->perl;
__________________________________________________________________
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]
