You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "James L. Morris" <jm...@grn.georet.net> on 2002/04/09 18:04:55 UTC
Your production apache server
Hello,
I'm new to Apache. I need some wisdom from some of the more experienced
Apache admins out there.
When you build an apache server, what do you typically compile in? I
know from reading the list that mod_perl and mod_php must be compiled in
at build time ... but is there anything else that cannot be loaded as a
module?
My biggest aggravation is getting my server built "just-so" only to find
out I need to recompile because I need a feature that cannot be loaded
as module. This has not happened yet ... but I want to avoid wasted
time as best as I can.
Thank you!
Jim
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Your production apache server
Posted by "James L. Morris" <jm...@grn.georet.net>.
Understand. I learned that the hard way after doing just a ./configure
with no options ... mod_so isn't there unless you specify it in the
configure command.
What is the Apache Toolkit and why should (or shouldn't) I use it.
I've heard some chatter about it but don't really know what it is.
I have used Webmin from time to time ... it has helped me with some
apache configuration problems ...
Jim
----- Original Message -----
From: "Daniel Lopez" <da...@rawbyte.com>
To: <us...@httpd.apache.org>
Sent: Tuesday, April 09, 2002 2:01 PM
Subject: Re: Your production apache server
>
> The apxs tool, bundled with Apache allows you to add additional modules
w/o
> having to recompile the whole server. The only thing you need to make sure
> is that Apache was compiled with loadable module support (--enable-so)
>
> Daniel
>
> > One tip to keep in mind - record the "./configure ..." line you use for
> > this build somewhere. Then, if you need to recompile you don't have to
> > figure it out all over again. Just base your new configuration off the
old
> > one.
> >
> > Occasional recompiles really aren't so bad if you save the
configuration.
> >
> > -Andy
> >
> > On Tue, 9 Apr 2002 14:00:02 -0400
> > "James L. Morris" <jm...@grn.georet.net> wrote:
> >
> > > Andrew,
> > >
> > > Thanks for the information. When I built my server, I needed
> > > WebDAV (for Dreamweaver 4) and mod_ldap for authentication.
> > > I compiled them both in. I may need perl or php in the future, so if
> > > I do ... I guess I'll have to recompile from scratch with all the
> > > original source code. It's an evil beast ... but a necessary evil.
> > >
> > > Thanks,
> > > Jim
> > > ----- Original Message -----
> > > From: "Andrew Hawkes" <ah...@unicon.net>
> > > To: <us...@httpd.apache.org>
> > > Sent: Tuesday, April 09, 2002 1:58 PM
> > > Subject: Re: Your production apache server
> > >
> > >
> > > > It depends on what you plan to do with the server. In general, you
> > > > should stick mostly with the default modules, which provide a fully
> > > > functional, configurable HTTP server.
> > > >
> > > > Anything that is not compiled "just-so" is a specialty module for a
> > > > unique purpose. If you have a need for these modules you will know
it.
> > > > In other words, only compile mod_perl if you will be running some
> > > > serious Perl code by experienced Perl programmers. Likewise only add
> > > > PHP if you'll be running PHP code. Only add mod_ssl if you need an
SSL
> > > > server. These are all extra modules that make for larger httpd
> > > > processes and should not be there unless you actually need them,
> > > > because of the overhead.
> > > >
> > > > -Andy
> > > >
> > > > On Tue, 9 Apr 2002 12:04:55 -0400
> > > > "James L. Morris" <jm...@grn.georet.net> wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > I'm new to Apache. I need some wisdom from some of the more
> > > > > experienced Apache admins out there.
> > > > >
> > > > > When you build an apache server, what do you typically compile in?
> > > > > I know from reading the list that mod_perl and mod_php must be
> > > > > compiled in at build time ... but is there anything else that
cannot
> > > > > be loaded as a module?
> > > > >
> > > > > My biggest aggravation is getting my server built "just-so" only
to
> > > > > find out I need to recompile because I need a feature that cannot
be
> > > > > loaded as module. This has not happened yet ... but I want to
avoid
> > > > > wasted time as best as I can.
> > > > >
> > > > > Thank you!
> > > > > Jim
> > > > >
> >
> > ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server
Project.
> > See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
> >
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Your production apache server
Posted by Daniel Lopez <da...@rawbyte.com>.
The apxs tool, bundled with Apache allows you to add additional modules w/o
having to recompile the whole server. The only thing you need to make sure
is that Apache was compiled with loadable module support (--enable-so)
Daniel
> One tip to keep in mind - record the "./configure ..." line you use for
> this build somewhere. Then, if you need to recompile you don't have to
> figure it out all over again. Just base your new configuration off the old
> one.
>
> Occasional recompiles really aren't so bad if you save the configuration.
>
> -Andy
>
> On Tue, 9 Apr 2002 14:00:02 -0400
> "James L. Morris" <jm...@grn.georet.net> wrote:
>
> > Andrew,
> >
> > Thanks for the information. When I built my server, I needed
> > WebDAV (for Dreamweaver 4) and mod_ldap for authentication.
> > I compiled them both in. I may need perl or php in the future, so if
> > I do ... I guess I'll have to recompile from scratch with all the
> > original source code. It's an evil beast ... but a necessary evil.
> >
> > Thanks,
> > Jim
> > ----- Original Message -----
> > From: "Andrew Hawkes" <ah...@unicon.net>
> > To: <us...@httpd.apache.org>
> > Sent: Tuesday, April 09, 2002 1:58 PM
> > Subject: Re: Your production apache server
> >
> >
> > > It depends on what you plan to do with the server. In general, you
> > > should stick mostly with the default modules, which provide a fully
> > > functional, configurable HTTP server.
> > >
> > > Anything that is not compiled "just-so" is a specialty module for a
> > > unique purpose. If you have a need for these modules you will know it.
> > > In other words, only compile mod_perl if you will be running some
> > > serious Perl code by experienced Perl programmers. Likewise only add
> > > PHP if you'll be running PHP code. Only add mod_ssl if you need an SSL
> > > server. These are all extra modules that make for larger httpd
> > > processes and should not be there unless you actually need them,
> > > because of the overhead.
> > >
> > > -Andy
> > >
> > > On Tue, 9 Apr 2002 12:04:55 -0400
> > > "James L. Morris" <jm...@grn.georet.net> wrote:
> > >
> > > > Hello,
> > > >
> > > > I'm new to Apache. I need some wisdom from some of the more
> > > > experienced Apache admins out there.
> > > >
> > > > When you build an apache server, what do you typically compile in?
> > > > I know from reading the list that mod_perl and mod_php must be
> > > > compiled in at build time ... but is there anything else that cannot
> > > > be loaded as a module?
> > > >
> > > > My biggest aggravation is getting my server built "just-so" only to
> > > > find out I need to recompile because I need a feature that cannot be
> > > > loaded as module. This has not happened yet ... but I want to avoid
> > > > wasted time as best as I can.
> > > >
> > > > Thank you!
> > > > Jim
> > > >
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Your production apache server
Posted by Mark Luntzel <ma...@neurosis.net>.
this is also kept in config.status if you still have the old source tree lying around.
With large, sharp teeth, Andrew Hawkes chortled:
> One tip to keep in mind - record the "./configure ..." line you use for
> this build somewhere. Then, if you need to recompile you don't have to
> figure it out all over again. Just base your new configuration off the old
> one.
>
> Occasional recompiles really aren't so bad if you save the configuration.
>
> -Andy
>
> On Tue, 9 Apr 2002 14:00:02 -0400
> "James L. Morris" <jm...@grn.georet.net> wrote:
>
> > Andrew,
> >
> > Thanks for the information. When I built my server, I needed
> > WebDAV (for Dreamweaver 4) and mod_ldap for authentication.
> > I compiled them both in. I may need perl or php in the future, so if
> > I do ... I guess I'll have to recompile from scratch with all the
> > original source code. It's an evil beast ... but a necessary evil.
> >
> > Thanks,
> > Jim
> > ----- Original Message -----
> > From: "Andrew Hawkes" <ah...@unicon.net>
> > To: <us...@httpd.apache.org>
> > Sent: Tuesday, April 09, 2002 1:58 PM
> > Subject: Re: Your production apache server
> >
> >
> > > It depends on what you plan to do with the server. In general, you
> > > should stick mostly with the default modules, which provide a fully
> > > functional, configurable HTTP server.
> > >
> > > Anything that is not compiled "just-so" is a specialty module for a
> > > unique purpose. If you have a need for these modules you will know it.
> > > In other words, only compile mod_perl if you will be running some
> > > serious Perl code by experienced Perl programmers. Likewise only add
> > > PHP if you'll be running PHP code. Only add mod_ssl if you need an SSL
> > > server. These are all extra modules that make for larger httpd
> > > processes and should not be there unless you actually need them,
> > > because of the overhead.
> > >
> > > -Andy
> > >
> > > On Tue, 9 Apr 2002 12:04:55 -0400
> > > "James L. Morris" <jm...@grn.georet.net> wrote:
> > >
> > > > Hello,
> > > >
> > > > I'm new to Apache. I need some wisdom from some of the more
> > > > experienced Apache admins out there.
> > > >
> > > > When you build an apache server, what do you typically compile in?
> > > > I know from reading the list that mod_perl and mod_php must be
> > > > compiled in at build time ... but is there anything else that cannot
> > > > be loaded as a module?
> > > >
> > > > My biggest aggravation is getting my server built "just-so" only to
> > > > find out I need to recompile because I need a feature that cannot be
> > > > loaded as module. This has not happened yet ... but I want to avoid
> > > > wasted time as best as I can.
> > > >
> > > > Thank you!
> > > > Jim
> > > >
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
--
bash: rtfm: command not found
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Your production apache server
Posted by "James L. Morris" <jm...@grn.georet.net>.
That's a good idea. I keep all my source code in a certain directory,
so that sounds like a good place to keep the configure file!
Thanks much,
Jim
----- Original Message -----
From: "Andrew Hawkes" <ah...@unicon.net>
To: <us...@httpd.apache.org>
Sent: Tuesday, April 09, 2002 2:08 PM
Subject: Re: Your production apache server
> One tip to keep in mind - record the "./configure ..." line you use for
> this build somewhere. Then, if you need to recompile you don't have to
> figure it out all over again. Just base your new configuration off the old
> one.
>
> Occasional recompiles really aren't so bad if you save the configuration.
>
> -Andy
>
> On Tue, 9 Apr 2002 14:00:02 -0400
> "James L. Morris" <jm...@grn.georet.net> wrote:
>
> > Andrew,
> >
> > Thanks for the information. When I built my server, I needed
> > WebDAV (for Dreamweaver 4) and mod_ldap for authentication.
> > I compiled them both in. I may need perl or php in the future, so if
> > I do ... I guess I'll have to recompile from scratch with all the
> > original source code. It's an evil beast ... but a necessary evil.
> >
> > Thanks,
> > Jim
> > ----- Original Message -----
> > From: "Andrew Hawkes" <ah...@unicon.net>
> > To: <us...@httpd.apache.org>
> > Sent: Tuesday, April 09, 2002 1:58 PM
> > Subject: Re: Your production apache server
> >
> >
> > > It depends on what you plan to do with the server. In general, you
> > > should stick mostly with the default modules, which provide a fully
> > > functional, configurable HTTP server.
> > >
> > > Anything that is not compiled "just-so" is a specialty module for a
> > > unique purpose. If you have a need for these modules you will know it.
> > > In other words, only compile mod_perl if you will be running some
> > > serious Perl code by experienced Perl programmers. Likewise only add
> > > PHP if you'll be running PHP code. Only add mod_ssl if you need an SSL
> > > server. These are all extra modules that make for larger httpd
> > > processes and should not be there unless you actually need them,
> > > because of the overhead.
> > >
> > > -Andy
> > >
> > > On Tue, 9 Apr 2002 12:04:55 -0400
> > > "James L. Morris" <jm...@grn.georet.net> wrote:
> > >
> > > > Hello,
> > > >
> > > > I'm new to Apache. I need some wisdom from some of the more
> > > > experienced Apache admins out there.
> > > >
> > > > When you build an apache server, what do you typically compile in?
> > > > I know from reading the list that mod_perl and mod_php must be
> > > > compiled in at build time ... but is there anything else that cannot
> > > > be loaded as a module?
> > > >
> > > > My biggest aggravation is getting my server built "just-so" only to
> > > > find out I need to recompile because I need a feature that cannot be
> > > > loaded as module. This has not happened yet ... but I want to avoid
> > > > wasted time as best as I can.
> > > >
> > > > Thank you!
> > > > Jim
> > > >
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Your production apache server
Posted by Matt Garretson <ma...@assembly.state.ny.us>.
> One tip to keep in mind - record the "./configure ..." line you use for
> this build somewhere. Then, if you need to recompile you don't have to
I second this recommendation. One thing i do is have a shell
script called "doit" in every source directory in which i have the
configure command, so i can tweak or repeat it easily. E.g. the
one currently in my httpd-2.0.35 tree looks something like below
(BTW i'm still tweaking it, so not all the options below actually
work as i'd like):
#!/bin/sh
CFLAGS='-O3 -march=i686' LDFLAGS='-static' \
./configure \
--prefix=/opt/apache2 \
--disable-so \
--enable-static \
--disable-shared \
--enable-static-support \
--enable-info \
--disable-userdir \
--disable-asis \
--disable-autoindex \
--disable-imap \
--disable-env \
--disable-include \
--enable-auth \
--enable-auth-dbm \
--enable-auth-digest \
--enable-ssl \
2>&1 |tee configure.log
# make 2>&1 |tee make.log
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Your production apache server
Posted by Andrew Hawkes <ah...@unicon.net>.
One tip to keep in mind - record the "./configure ..." line you use for
this build somewhere. Then, if you need to recompile you don't have to
figure it out all over again. Just base your new configuration off the old
one.
Occasional recompiles really aren't so bad if you save the configuration.
-Andy
On Tue, 9 Apr 2002 14:00:02 -0400
"James L. Morris" <jm...@grn.georet.net> wrote:
> Andrew,
>
> Thanks for the information. When I built my server, I needed
> WebDAV (for Dreamweaver 4) and mod_ldap for authentication.
> I compiled them both in. I may need perl or php in the future, so if
> I do ... I guess I'll have to recompile from scratch with all the
> original source code. It's an evil beast ... but a necessary evil.
>
> Thanks,
> Jim
> ----- Original Message -----
> From: "Andrew Hawkes" <ah...@unicon.net>
> To: <us...@httpd.apache.org>
> Sent: Tuesday, April 09, 2002 1:58 PM
> Subject: Re: Your production apache server
>
>
> > It depends on what you plan to do with the server. In general, you
> > should stick mostly with the default modules, which provide a fully
> > functional, configurable HTTP server.
> >
> > Anything that is not compiled "just-so" is a specialty module for a
> > unique purpose. If you have a need for these modules you will know it.
> > In other words, only compile mod_perl if you will be running some
> > serious Perl code by experienced Perl programmers. Likewise only add
> > PHP if you'll be running PHP code. Only add mod_ssl if you need an SSL
> > server. These are all extra modules that make for larger httpd
> > processes and should not be there unless you actually need them,
> > because of the overhead.
> >
> > -Andy
> >
> > On Tue, 9 Apr 2002 12:04:55 -0400
> > "James L. Morris" <jm...@grn.georet.net> wrote:
> >
> > > Hello,
> > >
> > > I'm new to Apache. I need some wisdom from some of the more
> > > experienced Apache admins out there.
> > >
> > > When you build an apache server, what do you typically compile in?
> > > I know from reading the list that mod_perl and mod_php must be
> > > compiled in at build time ... but is there anything else that cannot
> > > be loaded as a module?
> > >
> > > My biggest aggravation is getting my server built "just-so" only to
> > > find out I need to recompile because I need a feature that cannot be
> > > loaded as module. This has not happened yet ... but I want to avoid
> > > wasted time as best as I can.
> > >
> > > Thank you!
> > > Jim
> > >
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Your production apache server
Posted by "James L. Morris" <jm...@grn.georet.net>.
Andrew,
Thanks for the information. When I built my server, I needed
WebDAV (for Dreamweaver 4) and mod_ldap for authentication.
I compiled them both in. I may need perl or php in the future, so if
I do ... I guess I'll have to recompile from scratch with all the
original source code. It's an evil beast ... but a necessary evil.
Thanks,
Jim
----- Original Message -----
From: "Andrew Hawkes" <ah...@unicon.net>
To: <us...@httpd.apache.org>
Sent: Tuesday, April 09, 2002 1:58 PM
Subject: Re: Your production apache server
> It depends on what you plan to do with the server. In general, you should
> stick mostly with the default modules, which provide a fully functional,
> configurable HTTP server.
>
> Anything that is not compiled "just-so" is a specialty module for a unique
> purpose. If you have a need for these modules you will know it. In other
> words, only compile mod_perl if you will be running some serious Perl code
> by experienced Perl programmers. Likewise only add PHP if you'll be
> running PHP code. Only add mod_ssl if you need an SSL server. These are
> all extra modules that make for larger httpd processes and should not be
> there unless you actually need them, because of the overhead.
>
> -Andy
>
> On Tue, 9 Apr 2002 12:04:55 -0400
> "James L. Morris" <jm...@grn.georet.net> wrote:
>
> > Hello,
> >
> > I'm new to Apache. I need some wisdom from some of the more experienced
> > Apache admins out there.
> >
> > When you build an apache server, what do you typically compile in? I
> > know from reading the list that mod_perl and mod_php must be compiled in
> > at build time ... but is there anything else that cannot be loaded as a
> > module?
> >
> > My biggest aggravation is getting my server built "just-so" only to find
> > out I need to recompile because I need a feature that cannot be loaded
> > as module. This has not happened yet ... but I want to avoid wasted
> > time as best as I can.
> >
> > Thank you!
> > Jim
> >
> >
> >
> > ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server
> > Project. See <URL:http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> > For additional commands, e-mail: users-help@httpd.apache.org
> >
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Your production apache server
Posted by Andrew Hawkes <ah...@unicon.net>.
It depends on what you plan to do with the server. In general, you should
stick mostly with the default modules, which provide a fully functional,
configurable HTTP server.
Anything that is not compiled "just-so" is a specialty module for a unique
purpose. If you have a need for these modules you will know it. In other
words, only compile mod_perl if you will be running some serious Perl code
by experienced Perl programmers. Likewise only add PHP if you'll be
running PHP code. Only add mod_ssl if you need an SSL server. These are
all extra modules that make for larger httpd processes and should not be
there unless you actually need them, because of the overhead.
-Andy
On Tue, 9 Apr 2002 12:04:55 -0400
"James L. Morris" <jm...@grn.georet.net> wrote:
> Hello,
>
> I'm new to Apache. I need some wisdom from some of the more experienced
> Apache admins out there.
>
> When you build an apache server, what do you typically compile in? I
> know from reading the list that mod_perl and mod_php must be compiled in
> at build time ... but is there anything else that cannot be loaded as a
> module?
>
> My biggest aggravation is getting my server built "just-so" only to find
> out I need to recompile because I need a feature that cannot be loaded
> as module. This has not happened yet ... but I want to avoid wasted
> time as best as I can.
>
> Thank you!
> Jim
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server
> Project. See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: Your production apache server
Posted by Hasanuddin Tamir <sa...@trabas.com>.
Hi James,
On Tue, 9 Apr 2002, James L. Morris <jm...@grn.georet.net> wrote,
> Hello,
>
> I'm new to Apache. I need some wisdom from some of the more experienced
> Apache admins out there.
>
> When you build an apache server, what do you typically compile in? I
To my personal local need, I compile all standard modules statically.
> know from reading the list that mod_perl and mod_php must be compiled in
> at build time ... but is there anything else that cannot be loaded as a
> module?
Yes there is, the core (http_core.c). It must be there all the time.
Seriously, mod_perl and mod_php are third party modules. They are not part
of the standard distribution. You can compile them both long after you have
apache compiled and running well, provided that you've prepared apache to
handle such situation (see below).
> My biggest aggravation is getting my server built "just-so" only to find
> out I need to recompile because I need a feature that cannot be loaded
> as module. This has not happened yet ... but I want to avoid wasted
> time as best as I can.
Unfortunately, or perhaps fortunately, most features are implemented in
modules. In fact, one of the coolest features, the one that allows you to
add features (via modules of course) without recompiling apache, is
implemented in a module (mod_so).
--
san->http(www.trabas.com)
{If Linux doesn't have solution, you have the wrong problem}
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org