Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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.
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.
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.*
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.
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 :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.