UNIX for Dummies Questions & Answers

How can I find out what options were used to build the apache currently running on my computer?

I'd like to upgrade and want to make sure not to break any sites running on it.

I've been going through the sites to figure out just what is needed, but want to be sure not to miss anything before proceeding...

I'm not sure if you can - but it probably would not matter since most of the changes between versions should not effect you. About all you can do is insure you document this build, save your configuration files before hand, insure you read and understand the differences between the versions (you didn't state what version you are at and going to) ( see the Apache upgrade information this one is 1.3 to 2.0 ). The one thing you have to insure is that you can successfully backout of the upgrade so insure your backups are good before changing. Warn your clients that the upgrade is needed (due to whatever reasons - if security, then that's a very good reason) and have their input into the change. Let them know there may be problems - and don't worry

Yes, there is a way to know how apache was compiled and/or what modules are loaded. I have done this before, when upgrading apache to support new functionality like cURL.

Offhand, I don't recall all the ways to do this, but phpinfo.php certainly returns a lot of useful apache info, for example:

Code:

APACHE_INCLUDE 	no value
APACHE_TARGET 	no value
Apache Version 	Apache/1.3.28 (Unix) PHP/4.3.10
Apache Release 	10328100
Apache API Version 	19990320
Hostname:Port 	www.yoursite.com:80
User/Group 	mysql(27)/0
Max Requests 	Per Child: 30 - Keep Alive: on - Max Per Connection: 100
Timeouts 	Connection: 200 - Keep-Alive: 15
Server Root 	/usr/local/apache
Loaded Modules 	mod_php4, mod_setenvif, mod_auth, mod_access, mod_alias, mod_userdir, mod_actions, mod_imap, mod_asis, mod_cgi, mod_dir, mod_autoindex, mod_include, mod_status, mod_negotiation, mod_mime, mod_log_config, mod_env, http_core

Also, I recall checking the apache distribution Makefile at one point in time. I do recall that I found many sites on the net that discuss this because this is a common issue for many people.