Hello,
I'd like to configure my apache installation (which contains
several virtualhosts) to use mod_perl (compiled as DSO)
only with _some_ of the virtualhosts, but not all of them.
That is, I'd like to put a LoadModule directive into those
virtualhost sections which use mod_perl and leave it
Thomas I'd like to configure my apache installation (which contains
Thomas several virtualhosts) to use mod_perl (compiled as DSO) only
Thomas with _some_ of the virtualhosts, but not all of them.
Apache fork()s children to handle requests, hence they are all exact
copies of the parent
Hi,
On Wed, 26 Jan 2000, Bruno Connelly wrote:
You could always run separate Apache instances per vhost. :-)
Thanks for your comments.
From the added ":-)", I derive that this may not
be common practice :)
However, if I'd like to do so, I'd have to split up my httpd.conf
into a part with
Bruno You could always run separate Apache instances per vhost. :-)
Thomas From the added ":-)", I derive that this may not be common
Thomas practice :)
It's not uncommon, I'm just making the assumption that if you're
worried about resource consumption, this might not your desired
However, if I'd like to do so, I'd have to split up my httpd.conf
into a part with mod_perl-using-vhosts and a part with the remaining
vhosts and setup 2 startup scripts for 2 separate apache instances,
both listening on port 80 (or 443 for https).
I think you might find the answer to this
Hi Thomas,
On Wed, 26 Jan 2000, James G Smith wrote:
Thomas Corte [EMAIL PROTECTED] wrote:
So, if I switch to DSOs for (at least) mod_ssl and mod_perl, can I expect
to decrease top's values above significantly?
I don't think so. My understanding of DSOs in Apache was to allow
inclusion of
Hello,
On Wed, 26 Jan 2000, G.W. Haywood wrote:
If not, what is the real benefit of DSO
It's intended to save memory, by sharing it between processes.
Well, this is exactly what I want :). Currently, I have mod_ssl and
mod_perl linked statically into my httpd binary (under HP/UX 11),
