This is a diff of configuring.html between httpd-docs-2.0 and httpd-docs-1.3 (Note httpd-docs-1.3 contains new docs). IIRC, the same feature was added to httpd-2.0. Can someone confirm it? I'd like to sync second part of this diff but I'm not familiar with httpd-2.0 source code.
--- /src/cvs/httpd-docs-2.0/manual/configuring.html Thu Jan 11 15:26:43 2001 +++ /src/cvs/httpd-docs-1.3/htdocs/manual/configuring.html.en Thu Jan 11 15:25:27 2001 @@ -35,8 +35,10 @@ <td valign="top"> <strong>Related Directives</strong><br><br> +<A HREF="mod/core.html#accessconfig">AccessConfig</A><br> <A HREF="mod/core.html#ifdefine"><IfDefine></A><br> <a href="mod/core.html#include">Include</a><br> +<A HREF="mod/core.html#resourceconfig">ResourceConfig</A><br> <A HREF="mod/mod_mime.html#typesconfig">TypesConfig</A><br> </td></tr></table> @@ -44,12 +46,24 @@ >directives</A> in plain text configuration files. The main configuration file is usually called <CODE>httpd.conf</CODE>. The location of this file is set at compile-time, but may be overridden -with the <CODE>-f</CODE> command line flag. In addition, other -configuration files may be added using the <CODE><A -HREF="mod/core.html#include">Include</A></CODE> directive. Any -directive may be placed in any of these configuration files. Changes -to the main configuration files are only recognized by Apache when it -is started or restarted.</p> +with the <CODE>-f</CODE> command line flag. Some sites also have +<CODE>srm.conf</CODE> and <CODE>access.conf</CODE> files for <A +HREF="http://www.apache.org/info/three-config-files.html";>historical +reasons</A>. In addition, other configuration files may be added using +the <CODE><A HREF="mod/core.html#include">Include</A></CODE> +directive. Any directive may be placed in any of these configuration +files. Changes to the main configuration files are only recognized by +Apache when it is started or restarted.</p> + +<P>New with Apache 1.3.13 is a feature where if any configuration +file is actually a directory, Apache will enter that directory +and parse any files (and subdirectories) found there as configuration +files. One possible use for this would be to add VirtualHosts +by creating small configuration files for each host, and placing +them in such a configuration directory. Thus, you can add or +remove VirtualHosts without editing any files at all, simply +adding or deleting them. This makes automating such processes +much easier. <P> The server also reads a file containing mime document types; the @@ -189,7 +203,7 @@ <hr> <H2><a name="logs">Log files</a></H2> -<!-- XXX: This section should be moved to its own file --> +<!-- This section should be moved to its own file --> <H3>security warning</H3> Anyone who can write to the directory where Apache is writing a log file can almost certainly gain access to the uid that the server is -- Yoshiki Hayashi
