Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Distribution: Ubuntu 16.04.7 LTS, Kali, MX Linux with i3WM
Posts: 299
Rep:
apache2 - which conf file to use ?
Hello,
I'm using Ubuntu 7.04 server which comes with apache2. I done some directory surfring and found that there are two .conf files : apache2.conf and httpd.conf. I want to add the directives ServerName and DocumentRoot but into which of the conf files should I place the two directives ???
Distribution: Ubuntu 16.04.7 LTS, Kali, MX Linux with i3WM
Posts: 299
Original Poster
Rep:
Thanks reddazz. The httpd.conf file is empty ( 0Kb) whereas the apache2.conf ( 21Kb) contains all the other directives which are usually associated with the httpd.conf file, hence, the confusion.
It could be one of those things that Ubuntu has decided to do differently. Is httpd.conf a symlink to apache2.conf? Try making your changes in apache2.conf and see if they work.
Distribution: Ubuntu 16.04.7 LTS, Kali, MX Linux with i3WM
Posts: 299
Original Poster
Rep:
They are not symlinked but I can put the directive ServerName in either of the two files and everything seems to work ok. I'm just intrigued and curious.
Edit: Just been doing a bit of reading around. Apparently in Ubuntu/ Debian the httpd.conf file is now redundant and apache2.conf is where all the action is.
Last edited by uncle-c; 03-08-2008 at 08:47 AM.
Reason: additional material.
Edit: Just been doing a bit of reading around. Apparently in Ubuntu/ Debian the httpd.conf file is now redundant and apache2.conf is where all the action is.
This is one of those things that annoys me about some Linux distros. Everyone else has standardised on httpd.conf and they move away from that.
I think for ubuntu and debian, they use apache2.conf. And httpd.conf is in centos.
Well, for Ubuntu and Debian - at least when installed with LAMP via tasksel - there is ah httpd.conf, but it's blank on install, and I guess used for supplementary commands.
Sure, you could ignore it and just use the apache2.conf, or vhost files.
Hello everyone!
First of all excuse my English!
I just came by while searching for an answer for the same question!
And based on your argue guys, I did this small test just to see what file does apache depend on when it starts. I simply renamed httpd.conf to something else (e.g. http.conf_) and restarted apache. And the result? Apache failed to start!
Then did the same thing to the other file (apache2.conf), and again apache failed to start, which means that apache will actually read and apply any configs done in BOTH FILES!
And thanks for reading!!
P.S. did the test under Debian 5...
Last edited by unistinger; 07-15-2012 at 11:08 AM.
Reason: adding that last line!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.