mmillson> I have always heard it's better to compile Apache from
mmillson> source vs. using the rpms, but no one has ever quantified
mmillson> the advantages to doing this. Until someone does, and the
mmillson> advantages of compiling from source outweigh the advantages
mmillson> I've listed below for using the rpms, I still recommend
mmillson> using the rpms.
mmillson>
mmillson> There must be advantages to compiling Apache from
mmillson> source. Anyone want to be the advocate for this and explain
mmillson> why/when to compile from source?
The most compelling reason to compile your own server is to
incorporate local source-level modifications. Even if it's something
simple, like changing HARD_SERVER_LIMIT, or suexec settings.
Another reason would be to have more control over the installation
process. Suppose you had an arrangement like this
httpd -> apache-1.3.27
apache-1.3.24/
apache-1.3.26/
apache-1.3.28/
Each versioned directory is a separate ServerRoot, and "httpd" is a
symbolic link to the currently active one. To roll forward, repoint
the symlink, and restart the server. To back out an upgrade, repoint
the symlink, and restart the server. Changing the active version can
be done in a matter of seconds, and with very little disruption.
This sort of "symlink to active version" technique is common approach
for handling versioned installations, while maintaining a uniform path
for scripts, etc to use. This isn't specific to apache; you can the
approach with any piece of softare: bind, sendmail, ant, tomcat,
emacs, java, or whatever.
dthomas> I would also like to know some facts on this. I need to
dthomas> maintain many Linux boxes running Apache and Tomcat...having
dthomas> the ability to update Apache with a plain RPM from RedHat is
dthomas> a huge bonus.
When you build an apache with the standard ("Apache") layout, the
--prefix directory contains an entire server installation. The job
is then to put a copy of that directory tree on a each of the servers
that need it. There are tools like rdist(1) that are designed
specifically for this purpose. This isn't a bad write-up
http://www.benedikt-stockebrand.de/rdist-intro.html
The second edition of the Unix Systems Adminstrators Handbook
http://www.bookpool.com/.x/esf5tdpqim/sm/0130206016
had a chapter on file distribution. Hopefully that chapter made it
into the third edition. If so, it's also worth a read.
Given the choice of using an RPM vs. building your own, there are
advantages and disadvantages to either approach. Ultimately, it's a
matter of weighing them out and determining what works best in your
particular situation.
--
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
