Received: by taz.hyperreal.com (8.6.12/8.6.5) id GAA05389;
 Thu, 13 Jun 1996 06:52:31 -0700
Received: from sierra.zyzzyva.com by taz.hyperreal.com (8.6.12/8.6.5) with
 ESMTP id GAA05382; Thu, 13 Jun 1996 06:52:27 -0700
Received: from zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com
 (8.7.5/8.6.11) with ESMTP id IAA21303 for <new-httpd@hyperreal.com>;
 Thu, 13 Jun 1996 08:52:24 -0500 (CDT)
Message-Id: <199606131352.IAA21303@sierra.zyzzyva.com>
To: new-httpd@hyperreal.com
Subject: Re: Config file question... 
In-reply-to: jad's message of Thu, 13 Jun 1996 08:16:12 -0400.
         <Pine.LNX.3.93.960613081005.13344A-100000@curie.bcc.louisville.edu>
X-uri: http://www.zyzzyva.com/
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 13 Jun 1996 08:52:24 -0500
From: Randy Terbush <randy@zyzzyva.com>
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@hyperreal.com

> Sorry if this is a FAQ or other tidbit of general knowledge...but I can't
> help myself.
> 
> Why are there three config files?  If this a throwback to NCSA?  Could
> someone explain the reasoning behind having three files instead of one?
> Maybe it's just me, but one file with logically separated sections and
> intelligent groupings of directives makes *much* more sense than three
> separate files that rely on one another...
> 
> Thanks,
> Jason

Back compatibility with NCSA. I think that there was some discussion
in the group a couple of weeks ago about "Why?" Rob McCool did this.

You can disable it in Apache with:

AccessConfig /dev/null
ResourceConfig /dev/null