Remove mentions of the obsolete ResourceConfig/AccessConfig.

<td valign="top">

<strong>Related Directives</strong><br><br>

<A HREF="mod/core.html#accessconfig">AccessConfig</A><br>

<A HREF="mod/core.html#ifdefine">&lt;IfDefine&gt;</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>

>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.  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>

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>

<P>

The server also reads a file containing mime document types; the

<hr>

<H2><a name="logs">Log files</a></H2>

<!-- This section should be moved to its own file -->

<!-- XXX: 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

<td valign="top">

<strong>Related Directives</strong><br><br>

<A HREF="mod/core.html#accessconfig">AccessConfig</A><br>

<A HREF="mod/core.html#ifdefine">&lt;IfDefine&gt;</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>

>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.  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>

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>

<P>

The server also reads a file containing mime document types; the

<hr>

<H2><a name="logs">Log files</a></H2>

<!-- This section should be moved to its own file -->

<!-- XXX: 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