Hi all,

I'm having trouble figuring out the right mix of configuration settings to do what I want, which is to have 5 separate sets libraries (DEV, TEST, PROD, developer1_personal_dev, developer2_personal_dev) get shared by a large number of vhosts. The way I am doing it now is each vhost Include's the appropriate mod_perl config file for whatever set of libs it needs to be on. The Include'd files each will do PerlOptions +Parent and PerlSwitches -Mlib=/path/to/specific/libs and then load a bunch of PerlModules from those libs.

The trouble is, as each vhost loads this config file for its plain and SSL vhost directives, the amount of memory being used seems to be going up, and restarting apache is taking longer and longer. Intead of loading it over and over again (twice for vhosts with ssl!) I am hoping to find a way to tell apache to load PROD mp configuration, then load 100 PROD vhosts that will all share it, then load TEST mp configuration, then load 20 vhosts that use those libs, etc, but I am getting error like: 'mod_perl is already running, too late for PerlSwitches' when I am trying to start setting this up.

Am I doing something wrong, or is there an esablished best-practice for doing this kind of thing?

Thanks for any information.

Regards,
Chris Hagglund.

Reply via email to