Finding out how Apache was ./configure'd
 

Hey All-

I need to reconfigure, Apache, but I don't know how it was installed before. And If I reconfigure apache and miss a configure step, I could screw up the web server! Is there a way to findout how apache was previously configured so I can include those configure commands when I rebuild apache? I am adding PHP to the server. It is a RH9 Machine.

TIA-

Matt

httpd -V should show it's compile settings

On a side note, if Apache was added during the regular RH9 installation, just add the PHP packages from the package manager. No need to mess with the apache installation.

That works but....
 

HEre is my results:

Server version: Apache/1.3.27 (Unix)
Server built: Jun 30 2003 15:08:00
Server's Module Magic Number: 19990320:13
Server compiled with....
-D HAVE_MMAP
-D HAVE_SHMGET
-D USE_SHMGET_SCOREBOARD
-D USE_MMAP_FILES
-D HAVE_FCNTL_SERIALIZED_ACCEPT
-D HAVE_SYSVSEM_SERIALIZED_ACCEPT
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D HARD_SERVER_LIMIT=2048
-D HTTPD_ROOT="/usr"
-D SUEXEC_BIN="/usr/sbin/suexec"
-D DEFAULT_PIDLOG="/var/run/httpd.pid"
-D DEFAULT_SCOREBOARD="/var/run/httpd.scoreboard"
-D DEFAULT_LOCKFILE="/var/run/httpd.lock"
-D DEFAULT_ERRORLOG="/var/log/httpd/error_log"
-D TYPES_CONFIG_FILE="/etc/httpd/conf/mime.types"
-D SERVER_CONFIG_FILE="/etc/httpd/conf/httpd.conf"
-D ACCESS_CONFIG_FILE="/etc/httpd/conf/access.conf"
-D RESOURCE_CONFIG_FILE="/etc/httpd/conf/srm.conf"

I am unsure what to do fomr here. How do these translate to

./configure --with-apxs=/blah

style commands? I need to be able to recompile the same as before but with php. The installation I am dealing with is not however the default redhat install.

Thx-
Matt

Coulda swore on 1.3.x that command showed configure options as well.

Try this
rpm -qa | grep httpd

To see if someone before used RPM to install it. (the paths above look a lot like a redhat supplied RPM )

nada
 

That unfortunately returned no results :-(

I just tried httpd -V on another serve rI installed apache 2.0 on and it didn't give the configure options either.

-M

You still have the source floating around from the earlier compile? Might dig in the makefile to see if you can dig up the previous config

hmm
 

I poked around a bit in the Makefile, saw some familiar configuration settings but nothing that really looked like it was a cli ./configure option.

I'd be glad to entertain any more suggestiong, but if you are all out, I appreciate the help.

Matt
:newbie:

Hrmm, yeah, bout out of ideas. In times like this I would end up compiling the new apache with every option you think you might use on the machine, then add a few more.

I assume this is a live webserver, and that is where the risk in bonking it lies?

In Apache 2 a file config.nice is generated saving your original configuration options that can be run again, as far as 1.3 all I can see is a reference to Configuration.apaci which might possibly be what you're looking for.

praefex,

The configure command line should be in config.log, at the top of the file. (Just checked my 2.0 build, not positive what 1.3 uses) It doesn't show env variables, but hopefully you don't need to set any of those. If you can't see it there, try greping config.*

Good Luck,
chris

live server
 

Yeah this is a live server, and its scary doing an upgrade, when that server is making you money. I'll try looking at those files to see if they tell me how it was installed.

Thanks Everyone!

-Matt

turns out...
 

That apache 1.3 store the config info in the config.status file after you do a ./configure, at least it was a reasonable approximation of it for anyone interested.

Still haven't got it up and running. :-( But I need to look at it again, maybe I'll just go Apache 2.0.47 or something :-)

Thanks everyone!
Matt