httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rbo...@apache.org
Subject cvs commit: httpd-docs-1.3/htdocs/manual/mod core.html.en
Date Sat, 09 Feb 2002 20:32:24 GMT
rbowen      02/02/09 12:32:24

  Modified:    htdocs/manual/mod core.html.en
  Log:
  Additional comments and examples for the Include directive.
  
  Revision  Changes    Path
  1.213     +42 -0     httpd-docs-1.3/htdocs/manual/mod/core.html.en
  
  Index: core.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/core.html.en,v
  retrieving revision 1.212
  retrieving revision 1.213
  diff -u -r1.212 -r1.213
  --- core.html.en	8 Feb 2002 18:02:55 -0000	1.212
  +++ core.html.en	9 Feb 2002 20:32:23 -0000	1.213
  @@ -1700,10 +1700,52 @@
       <p>This directive allows inclusion of other configuration files
       from within the server configuration files.</p>
   
  +    <p>The file path specified may be a fully qualified path (i.e.
  +    starting with a slash), or may be relative to the
  +    <code>ServerRoot</code> directory.</p>
  +
       <p>New in Apache 1.3.13 is the feature that if
       <code>Include</code> points to a directory, rather than a file,
       Apache will read all files in that directory, and any
       subdirectory, and parse those as configuration files.</p>
  +
  +    <p>Examples:</p>
  +
  +    <blockquote>
  +    <code>Include /usr/local/apache/conf/ssl.conf<br />
  +    Include /usr/local/apache/conf/vhosts/
  +    </blockquote>
  +
  +    <p>Or, providing paths relative to your <code>ServerRoot</code>
  +    directory:</p>
  +
  +    <blockquote>
  +    <code>Include conf/ssl.conf<br />
  +    Include conf/vhosts/
  +    </blockquote>
  +
  +    <p>Make sure that an included directory does not contain any stray
  +    files, such as editor temporary files, for example, as Apache will
  +    attempt to read them in and use the contents as configuration
  +    directives, which may cause the server to fail on start up.
  +    Running <code>apachectl configtest</code> will give you a list of
  +    the files that are being processed during the configuration  
  +    check:<p>
  +
  +<pre>
  +root@host# apachectl configtest
  + Processing config directory: /usr/local/apache/conf/vhosts
  + Processing config file: /usr/local/apache/conf/vhosts/vhost1
  + Processing config file: /usr/local/apache/conf/vhosts/vhost2
  +Syntax OK
  +</pre>
  +
  +    <p>This will help in verifying that you are getting only the files
  +    that you intended as part of your configuration.</p>
  +
  +    <p><strong>See also</strong>: <a
  +    href="../programs/apachectl.html">apachectl</a></p>
  +
       <hr />
   
       <h2><a id="keepalive" name="keepalive">KeepAlive
  
  
  

Mime
View raw message