httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yosh...@apache.org
Subject cvs commit: httpd-2.0/docs/manual configuring.html
Date Mon, 15 Jan 2001 08:58:14 GMT
yoshiki     01/01/15 00:58:14

  Modified:    docs/manual configuring.html
  Log:
  Backport documentation about Include som-dir usage from 1.3.
  
  Revision  Changes    Path
  1.7       +18 -6     httpd-2.0/docs/manual/configuring.html
  
  Index: configuring.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/configuring.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- configuring.html	2001/01/11 06:12:55	1.6
  +++ configuring.html	2001/01/15 08:58:14	1.7
  @@ -44,12 +44,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
  
  
  

Mime
View raw message