|Subject:||building Apache from source, on a machine where Apache was installed with yum|
|Posted by:||Bennett Haselton (benne…@peacefire.org)|
|Date:||Sun, 11 Jul 2010|
I have a CentOS 5.5 dedicated server that was set up for me by a
webhosting company, where I installed Apache 2.2.3 with yum (i.e. not
building from source, there is no Apache source code on the machine).
I've run up against some problems which I've been advised will require
re-building Apache from source (e.g. in mod_status I want to see the
full path to each request instead of only the first 63 characters, and
unless apparently you change the source code of Apache, it only makes
the first 63 characters of each request available to modules).
Which of these two options is considered a better practice, or is
there some reason why one will not even work at all and I'll have to
use the other one:
1) building a new copy of Apache from source under my home directory,
and changing /etc/init.d and anything that else that points to the old
Apache at /usr/sbin/httpd , to point to my new Apache location as well
2) backing up the /usr/sbin/httpd binary (and any other binaries that
get built by the build process) and building Apache from source to
overwrite the /usr/sbin/httpd binary.
I am hoping there's a way to do #2, because I have a lot of custom
scripts that all expect Apache to be at /usr/sbin/httpd and all expect
it's configuration file to be /etc/httpd/conf/httpd.conf, and it would
be a pain to change all of those.