stas 2002/12/13 01:58:29
Modified: . STATUS
Log:
document the problem with mod_perl starting from vhost
Revision Changes Path
1.26 +23 -1 modperl-2.0/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/modperl-2.0/STATUS,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- STATUS 12 Dec 2002 08:30:47 -0000 1.25
+++ STATUS 13 Dec 2002 09:58:29 -0000 1.26
@@ -56,6 +56,28 @@
Needs Patch or Further Investigation:
-------------------------------------
+* we still have a problem with mod_perl starting from a
+ vhost. consider the following config:
+
+ PerlSwitches -I/foo/bar
+ <VirtualHost TestDirective::perlloadmodule6>
+ PerlLoadModule TestDirective::perlloadmodule6
+ ...
+ </VirtualHost>
+
+ The value set by PerlSwitches in the main server is ignored, because
+ it's not seen by mod_perl starting from vhost.
+
+ overall, currently the early startup in vhost is a bunch of ugly
+ workaround, which I've added everytime I came up with a config that
+ wasn't working. Need to come up with a better design decisions.
+
+ once this is fixed. I want the perlloadmodule6 to be loaded before
+ all other perlloadmodule configs, because it tests an important
+ segfault when perlloadmodule happens to start mod_perl from within a
+ vhost. but because PerlSwitches from other tests are ignored, it
+ can't trigger the mod_perl startup in the test suite.
+
* slurp_filename's C implementation.
Status: 1.x's like patch posted: doug -1
