> In other words, it does not really make sense to expect a different lib path > per virtual > host, since the perl modules and scripts exist on a "one per process" base, > not a "one per > virtual host" base. > Or, you have to really set the lib path dynamically, on a per-request base, > not just when > your script is first compiled.
Thx Andre. What do you make of this page then: http://perl.apache.org/docs/2.0/user/config/config.html#Modifying_C__INC__on_a_Per_VirtualHost which says: --- If Perl used with mod_perl was built with ithreads support one can specify different @INC values for different VirtualHosts, using a combination of PerlOptions +Parent and PerlSwitches. --- Is this wrong? Maybe it's that my version is not compiled with ithreads support? I know I have a thread-enabled version of perl, because when I run the following script: --- use Config; if ($Config{useithreads}) { print "threads compiled" } else { print "NOT threads compiled" } --- It tells me that it IS threads compiled. But I know that there are two versions of thread support (an older one, and a newer one), and I am not sure which of the two is meant by 'built with ithreads support'. Alain
