Progeny Debian Linux uses all three Apache .conf files. Why?

Hi all,

My first post here, so be kind . . .

I have just installed Progeny's Debian Linux on a new server and the distribution of Apache that comes with it is 1.3.20 (the latest).

What's weird is that this install of Apache is using all three of the .conf files (httpd.conf, srm.conf, and access.conf) and not just the amalgamated httpd.conf where srm.conf and access.conf are just empty.

The server works fine, but this is messing with my mind since the Apache.org folks don't use all three files since 1.3.0 (or at least that's my understanding). I just got used to the amalgated .conf file on my other server and I don't want to go backwards in time unless I have to

Anyone know why Progeny's version of Debian Linux installs the latest release of Apache server this way

BTW, just wanted to say that these are great forums! I use UBB 6.0x on my site but this version of vBulletin simply rocks! Sadly, changing message boards for us self-taught server admins (translation: I know just enough to be dangerous) is an overwhelming prospect indeed.

Just put the following to your httpd.conf:

ResourceConfig /dev/null
AccessConfig /dev/null

and that's it. srm.conf and access.conf will not be read.

FreeBSD,

Not sure if I should include those lines in the httpd.conf file because as it stands now it is incomplete . . . srm.conf and access.conf actually have important info in them . . .

D'oh!

Ya think I could copy the info (or "cat" it) from access.conf and srm.conf over to httpd.conf and then use the /dev/null lines? Hmmm? I suppose I could, eh? I can hear freebsd now, By Jove! I think 'e's got it!

BUT WAIT, not so fast . . . this still begs the question: Why the heck does Progeny's Debian Linux have the latest version of Apache configured this way? Like I said before, it's messing with my mind!

>> I could copy the info (or "cat" it) from access.conf and srm.conf over to httpd.conf

Yes. Maybe you should start here -> http://httpd.apache.org/docs/mod/co...#resourceconfig and here -> http://httpd.apache.org/docs/mod/core.html#accessconfig

>> Why the heck does Progeny's Debian Linux have the latest version of Apache configured this way?

That was an old implemention in Apache and they dropped that for quite a while. You still can use it as it gives you a neat httpd.conf, not dynamic way of parsing server config file. I have no idea why Debian is doing it. Nobody installing Apache should care about that (since all should install Apache by compiling from src anyway). Apache is highly configurable and there are just way too many configure options, installing from a binary distribution is just not a wise thing to do.

freebsd,

Yes, you are 110% correct, Apache should be compiled from src. I've never wasted more time than the week I tried getting an Apache RPM to work with a PHP RPM on a Red Hat 7.0 Linux box. You'd think I'd learn, huh?

Actually, I may be starting to learn: after perusing these forums for the past few days (and reading plenty of "freebsd's" posts), I decided to trash my Debian setup and go with FreeBSD (the OS, not the forum poster!).

I must say, it really is the bee's knees---very powerful, unparalled flexibility and stellar documentation that a non-computer science degree holder like me can even understand. It's certainly not as plug and play as RedHat or Debian, but then again, it makes you learn how things work which is a plus if you intend to use these sorts of OS's on a regular basis. Just my $.02.