This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Date: Thu, 14 Sep 2000 23:26:33 +0200 (CEST) From: Ime Smits <ime@iaehv.iae.nl> To: William Deegan <bdeegan@iescrow.com> Cc: "G.W. Haywood" <ged@www.jubileegroup.co.uk>, modperl@apache.org Subject: Re: perl initialization per virtual host... is it possible | I meant a different startup per virtual host, not per child process. It's perfectly ok to specify a PerlRequire for each virtual host or even in .htaccess, but I think that's a dirty habbit to get into. As the complete perl namespace is shared between all your virtual hosts there is really no benifit, just drawbacks: modules required before Apache forks off will result in all childs using a single copy of that module, but required modules after that will load a copy for each child process. === To: "William Deegan" <bdeegan@iescrow.com> Cc: "G.W. Haywood" <ged@www.jubileegroup.co.uk>, <modperl@apache.org> Subject: Re: perl initialization per virtual host... is it possible From: David Hodgkinson <daveh@hodgkinson.org> Date: 14 Sep 2000 22:31:25 +0100 "William Deegan" <bdeegan@iescrow.com> writes: > I meant a different startup per virtual host, not per child process. > > Is that possible? If you're going to do that, say, to stop virtual servers interfering with each other, consider having COMPLETELY different fat servers hidden behind your thin one. === From: "William Deegan" <bdeegan@iescrow.com> To: "Ime Smits" <ime@iaehv.iae.nl> Cc: <modperl@apache.org> References: <Pine.BSF.4.05.10009142319230.93535-100000@iaehv.iae.nl> Subject: Re: perl initialization per virtual host... is it possible Date: Thu, 14 Sep 2000 14:47:07 -0700 "Ime Smits" <ime@iaehv.iae.nl> wrote: > > > | I meant a different startup per virtual host, not per child process. > > It's perfectly ok to specify a PerlRequire for each virtual host > or even in .htaccess, but I think that's a dirty habbit to get > into. As the complete perl namespace is shared between all > your virtual hosts there is really no benifit, just drawbacks: > modules required before Apache forks off will result in all > childs using a single copy of that module, but required modules > after that will load a copy for each child process. When I do that a "SetEnv" in my virtual host doesn't seem to get passed to the startup.pl... Is that the expected behavior? === Date: Mon, 25 Sep 2000 13:05:36 -0700 (PDT) From: Doug MacEachern <dougm@covalent.net> To: William Deegan <bdeegan@iescrow.com> cc: Ime Smits <ime@iaehv.iae.nl>, modperl@apache.org Subject: Re: perl initialization per virtual host... is it possible On Thu, 14 Sep 2000, William Deegan wrote: > When I do that a "SetEnv" in my virtual host doesn't seem to get > passed to the startup.pl... > > Is that the expected behavior? yes, SetEnv isn't passed until the request time fixup phase. try PerlSetEnv, which will be set at startup time outside of Directory/Location/Files/etc. sections. ===