Torsten Foertsch schrieb:
On Mon 19 Jan 2009, Adam Prime wrote:
I thought you could build more than one and load the one you want
at runtime. Isn't that what Red Hat does?
If redhat's shipping more than one mpm, they've patched httpd.
Probably not httpd. At least Suse has not. Instead they c
Philip,
thanks a lot for this thorough and exhaustive answer!
Philip M. Gollucci schrieb:
Michael Ludwig wrote:
So, to summarize: The mod_perl DSO depends on the particular versions of
Perl and Apache.
The modules in the Apache2:: namespace
most definitely dpends on libperl.so, httpd, apr,
William A. Rowe, Jr. wrote:
Built with a threaded MPM and any module should also work on prefork etc.
But not visa-versa!!!
100% correct, the linkage is wrong the other way.
--
Philip M. Gollucci (pgollu...@p6m7g8.com)
Torsten Foertsch wrote:
> On Mon 19 Jan 2009, Adam Prime wrote:
>>> I thought you could build more than one and load the one you want
>>> at runtime. Isn't that what Red Hat does?
>> If redhat's shipping more than one mpm, they've patched httpd.
>
> Probably not httpd. At least Suse has not. Inst
On Mon 19 Jan 2009, Adam Prime wrote:
> > I thought you could build more than one and load the one you want
> > at runtime. Isn't that what Red Hat does?
>
> If redhat's shipping more than one mpm, they've patched httpd.
Probably not httpd. At least Suse has not. Instead they configure and
build
Why not just run multiple httpds? I do it, but I have multiple IPs
and that may be a requirement for running different httpds.
On Jan 19, 2009, at 12:45 PM, Adam Prime wrote:
Perrin Harkins wrote:
On Mon, Jan 19, 2009 at 1:37 PM, Adam Prime
wrote:
Perrin Harkins wrote:
Hmm, isn't the MP
Perrin Harkins wrote:
On Mon, Jan 19, 2009 at 1:37 PM, Adam Prime wrote:
Perrin Harkins wrote:
Hmm, isn't the MPM just a runtime configuration? Why would you need
another httpd install? It sounds like a separate config file would do
it, if that's all you want to change.
MPM is a build time
On Mon, Jan 19, 2009 at 1:37 PM, Adam Prime wrote:
> Perrin Harkins wrote:
>>
>> Hmm, isn't the MPM just a runtime configuration? Why would you need
>> another httpd install? It sounds like a separate config file would do
>> it, if that's all you want to change.
>
> MPM is a build time configura
Perrin Harkins wrote:
Hmm, isn't the MPM just a runtime configuration? Why would you need
another httpd install? It sounds like a separate config file would do
it, if that's all you want to change.
MPM is a build time configuration via the --with-mpm= to ./configure
Adam
On Mon, Jan 19, 2009 at 5:56 AM, Michael Ludwig wrote:
> Now, what happens if I am going to install a new Apache
> 2.2/prefork with mod_perl in addition to the already existing
> Apache 2.2/worker with mod_perl?
Hmm, isn't the MPM just a runtime configuration? Why would you need
another httpd in
Michael Ludwig wrote:
The mod_perl DSO itself is installed to $ServerRoot/modules. Doing
an ldd on the module doesn't reveal any dependencies on libraries
under $ServerRoot/lib, but I guess that nevertheless, this mod_perl
does very well depend on the particular Apache version it is
configured an
What does a mod_perl 2.0 installation on Linux consist of?
* Apache 2.0 or 2.2
* mod_perl 2.0
* libapreq (optional, true, but indispensable for convenience)
The Apache, let's say the worker MPM, is going to be installed
under /usr/local/apache22w. If I now want to install a prefork
MPM next to i
12 matches
Mail list logo
