Author: stas
Date: Mon Feb 21 17:40:34 2005
New Revision: 154756
URL: http://svn.apache.org/viewcvs?view=rev&rev=154756
Log:
Modifying C<@INC> on a Per-VirtualHost is possible under any mpm as long
as perl has ithreads enabled
Modified:
perl/modperl/docs/trunk/src/docs/2.0/user/config/config.pod
Modified: perl/modperl/docs/trunk/src/docs/2.0/user/config/config.pod
URL:
http://svn.apache.org/viewcvs/perl/modperl/docs/trunk/src/docs/2.0/user/config/config.pod?view=diff&r1=154755&r2=154756
==============================================================================
--- perl/modperl/docs/trunk/src/docs/2.0/user/config/config.pod (original)
+++ perl/modperl/docs/trunk/src/docs/2.0/user/config/config.pod Mon Feb 21
17:40:34 2005
@@ -1467,6 +1467,12 @@
bypasses perl's security and will affect C<@INC>. Use it only if you
know what you are doing.
+
+
+
+
+
+
=head2 Modifying C<@INC> on a Per-VirtualHost
If Perl used with mod_perl was built with ithreads support one can
@@ -1487,6 +1493,20 @@
PerlSwitches -I/home/dev2/lib/perl
PerlModule Apache2
</VirtualHost>
+
+This technique works under any MPM with ithreads-enabled perl. It's
+just that under prefork your procs will be huge, because you will
+build a pool of interpreters in each process. While the same happens
+under threaded mpm, there you have many threads per process, so you
+need just 1 or 2 procs and therefore less memory will be used.
+
+
+
+
+
+
+
+
=head1 General Issues
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
