httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wr...@locus.apache.org
Subject cvs commit: apache-1.3/htdocs/manual windows.html
Date Sat, 10 Jun 2000 05:15:06 GMT
wrowe       00/06/09 22:15:05

  Modified:    htdocs/manual windows.html
  Log:
    Just cleaning up some text file formatting, clarifing the Ctrl+C version
    levels, and pointing users at the httpd.conf file for it's directives
    -AND- documentation value :-)
  
  Revision  Changes    Path
  1.38      +126 -117  apache-1.3/htdocs/manual/windows.html
  
  Index: windows.html
  ===================================================================
  RCS file: /home/cvs/apache-1.3/htdocs/manual/windows.html,v
  retrieving revision 1.37
  retrieving revision 1.38
  diff -u -r1.37 -r1.38
  --- windows.html	2000/06/09 18:33:02	1.37
  +++ windows.html	2000/06/10 05:15:05	1.38
  @@ -31,13 +31,13 @@
      Before you submit a bug report or request, first consult this document, the 
      <A HREF="misc/FAQ.html">Frequently Asked Questions</A> page and the other

      relevant documentation topics.  If you still have a question or problem, 
  -   please post it to the <A HREF="news:comp.infosystems.www.servers.windows">
  -   comp.infosystems.www.servers.windows</A> newsgroup, where many Apache 
  -   users and several contributions are more than willing to answer new and 
  -   obscure questions about using Apache on Windows.</P>
  +   post it to the <A HREF="news:comp.infosystems.www.servers.ms-windows">
  +   comp.infosystems.www.servers.ms&minus;windows</A> newsgroup, where many 
  +   Apache users and several contributions are more than willing to answer new 
  +   and obscure questions about using Apache on Windows.</P>
   
  -<P>The <A HREF="http://www.deja.com/group/comp.infosystems.www.servers.ms-windows">
  -   deja.com archives</A> offer easy browsing of previous questions.  
  +<P><A HREF="http://www.deja.com/group/comp.infosystems.www.servers.ms-windows">
  +   deja.com's newsgroup archives</A> offer easy browsing of previous questions.
      Searching the newsgroup archives, you will usually find your question was 
      already asked and answered by other users!</P>
   
  @@ -88,8 +88,11 @@
   
   <P>If running on Windows 95, the "Winsock2" upgrade must be installed
      before Apache will run. "Winsock2" for Windows 95 is available
  -	 <A HREF="http://www.microsoft.com/windows95/downloads/contents/WUAdminTools/S_WUNetworkingTools/W95Sockets2/Default.asp">here</a>
  -   or via <A HREF="http://www.microsoft.com/windows95/downloads/">here</A>.</P>
  +   <A HREF="http://www.microsoft.com/windows95/downloads/contents/WUAdminTools/S_WUNetworkingTools/W95Sockets2/Default.asp">here</a>
  +   or via <A HREF="http://www.microsoft.com/windows95/downloads/">here</A>.
  +   Be warned that the Dialup Networking 1.2 (MS DUN) updates include a Winsock2
  +   that is entirely insufficient, and the Winsock2 update must be reinstalled
  +   after installing Windows 95 dialup networking.</P>
   
   
   <H2><A NAME="down">Downloading Apache for Windows</A></H2>
  @@ -131,155 +134,166 @@
   </UL>
   
   <P>During the installation, Apache will configure the files in the
  -<SAMP>conf</SAMP> directory for your chosen installation
  -directory. However if any of the files in this directory already exist
  -they will <STRONG>not</STRONG> be overwritten. Instead the new copy of
  -the corresponding file will be left with the extension
  -<SAMP>.default</SAMP>. So, for example, if
  -<SAMP>conf\httpd.conf</SAMP> already exists it will not be altered,
  -but the version which would have been installed will be left in
  -<SAMP>conf\httpd.conf.default</SAMP>. After the installation has
  -finished you should manually check to see what in new in the
  -<SAMP>.default</SAMP> file, and if necessary update your existing
  -configuration files.
  +   <SAMP>conf</SAMP> directory for your chosen installation
  +   directory. However if any of the files in this directory already exist
  +   they will <STRONG>not</STRONG> be overwritten. Instead the new copy of
  +   the corresponding file will be left with the extension
  +   <SAMP>.default</SAMP>. So, for example, if
  +   <SAMP>conf\httpd.conf</SAMP> already exists it will not be altered,
  +   but the version which would have been installed will be left in
  +   <SAMP>conf\httpd.conf.default</SAMP>. After the installation has
  +   finished you should manually check to see what in new in the
  +   <SAMP>.default</SAMP> file, and if necessary update your existing
  +   configuration files.</P>
   
   <P>Also, if you already have a file called <SAMP>htdocs\index.html</SAMP>
  -then it will not be overwritten (no <SAMP>index.html.default</SAMP>
  -file will be installed either). This should mean it is safe to install
  -Apache over an existing installation (but you will have to stop the
  -existing server running before doing the installation, then start the
  -new one after the installation is finished).
  +   then it will not be overwritten (no <SAMP>index.html.default</SAMP>
  +   file will be installed either). This should mean it is safe to install
  +   Apache over an existing installation (but you will have to stop the
  +   existing server running before doing the installation, then start the
  +   new one after the installation is finished).</P>
   
   <P>After installing Apache, you should edit the configuration files in
  -the <SAMP>conf</SAMP> directory as required. These files will be
  -configured during the install ready for Apache to be run from the
  -directory where it was installed, with the documents served from the
  -subdirectory <SAMP>htdocs</SAMP>. There are lots of other options
  -which should be set before you start really using Apache. However to
  -get started quickly the files should work as installed.
  +   the <SAMP>conf</SAMP> directory as required. These files will be
  +   configured during the install ready for Apache to be run from the
  +   directory where it was installed, with the documents served from the
  +   subdirectory <SAMP>htdocs</SAMP>. There are lots of other options
  +   which should be set before you start really using Apache. However to
  +   get started quickly the files should work as installed.</P>
   
   <H2><A NAME="run">Running Apache for Windows</A></H2>
   
   There are two ways you can run Apache:
   
   <UL>
  - <LI>As a <A HREF="win_service.html">"service"</A> (mainly available
on NT only, 
  -   highly experimental version for 95/98).
  + <LI>As a <A HREF="win_service.html">"service"</A> (tested on NT/2000
only, 
  +   but an <EM>experimental</EM> version is available for 95/98).
      This is the best option if you want Apache to automatically start when your
      machine boots, and to keep Apache running when you log-off.
    <LI>From a <A HREF="#cmdline">console window</A>. This is the best option
      available for Windows 95/98 users.
   </UL>
   
  -<P><STRONG>Complete the steps below before you proceed to attempt to 
  -   start Apache as a Window NT/2000 "<A HREF="win_service.html">service</A>"!</STRONG></P>
  +<P><STRONG>Complete the steps below before you attempt to start Apache 
  +   as a Windows "<A HREF="win_service.html">service</A>"!</STRONG></P>
   
   <P>To run Apache from a console window, select the "Start Apache as
      console app" option from the Start menu (in Apache 1.3.4 and earlier,
      this option was called "Apache Server"). This will open a console
      window and start Apache running inside it. The window will remain
  -   active until you stop Apache. To stop Apache running, either select
  +   active until you stop Apache. To stop Apache running, either press select
      the "Shutdown Apache console app" icon option from the Start menu
      (this is not available in Apache 1.3.4 or earlier), or see
  -	 <A HREF="#signal">signalling Console Apache when Running</A> for how
  -   to control Apache from the command line.
  -</P>
  +   <A HREF="#signal">signalling Console Apache when Running</A> for how
  +   to control Apache from the command line.</P>
  +
  +<P>In Apache 1.3.13 and above it is now quite safe to press Ctrl+C or 
  +   Ctrl+Break to stop the Apache in the console window.  And on Windows NT/2000
  +   with version 1.3.13, Apache will also gladly stop if you select 'Close'
  +   from the system menu (clicking the icon on the top-left corner of the
  +   console window) or click the close (X) button on the top-right corner.
  +   But do <EM>not</em> try any of these approaches on earlier versions of the
  +   Apache server, since Apache did not shut down cleanly.</P>
   
   <H2><A NAME="test">Testing Apache for Windows</A></H2>
   
  -<P>If you have trouble starting Apache please use the following steps to isolate
  -   the problem. This applies if you started Apache using the
  +<P>If you have trouble starting Apache please use the following steps to 
  +   isolate the problem. This applies if you started Apache using the
      "Start Apache as a console app" shortcut from the Start menu and
      the Apache console window closes immediately (or unexpectedly)
  -	 or if you have trouble starting Apache as a service.<br>
  -</P>
  +   or if you have trouble starting Apache as a service.</P>
   	 
   <P>Run the "Command Prompt" from the Start Menu - Programs list.  Change
  -   to the folder to which you installed Apache, type the command apache, and read
  -	 the error message.  Then review the error.log file for configuration mistakes.
  -	 If you accepted the defaults when you installed Apache, the commands would be:
  -</P>
  +   to the folder to which you installed Apache, type the command apache, and 
  +   read the error message.  Then review the error.log file for configuration 
  +   mistakes.  If you accepted the defaults when you installed Apache, the 
  +   commands would be:</P>
   
   <PRE>
     c:
     cd "\program files\apache group\apache"
     apache
  -  <SAMP>Wait for Apache to exit, or press Ctrl+C</SAMP>
  +  <EM>Wait for Apache to exit, or press </EM>Ctrl+C
     more &lt;logs\error.log
   </PRE>
   
  -<P>After looking at the error.log you will probably have a good chance of working
  -   out what went wrong and be able to fix the problem and try again. If you are unable
  -	 to work it out then please follow the <A HREF="#help">guidelines for assistance</A>
at
  -	 the top of this document or in the <a href="misc/FAQ.html#what2do">FAQ</a>.
  -	 Whatever you do, do not give up! Once you get Apache running
  -	 you will love it.
  -</P>
  +<P>After looking at the error.log you will probably have a good chance of 
  +   working out what went wrong and be able to fix the problem and try again. 
  +   If you are unable to work it out then please follow the 
  +   <A HREF="#help">guidelines for assistance</A> at the top of this document

  +   or in the <a href="misc/FAQ.html#what2do">FAQ</a>. Many users discover that
  +   the nature of the httpd.conf file is easier to manage and audit than page 
  +   after page of configuration dialog boxes.</P>
   
   <P>After starting Apache running (either in a console window or as a
      service) if will be listening to port 80 (unless you changed the
      <SAMP>Port</SAMP>, <SAMP>Listen</SAMP> or <SAMP>BindAddress</SAMP>
      directives in the configuration files). To connect to the server and
  -   access the default page, launch a browser and enter this URL:
  -</P>
  +   access the default page, launch a browser and enter this URL:</P>
   
   <PRE>
     http://localhost/
   </PRE>
   
  -This should respond with a welcome page, and a link to the Apache
  -manual. If nothing happens or you get an error, look in the
  -<SAMP>error_log</SAMP> file in the <SAMP>logs</SAMP> directory.
  -If your host isn't connected to the net, you may have to use
  -this URL:
  +<P>This should respond with a welcome page, and a link to the Apache
  +   manual. If nothing happens or you get an error, look in the
  +   <SAMP>error.log</SAMP> file in the <SAMP>logs</SAMP> directory.
  +   If your host isn't connected to the net, you may have to use
  +   this URL:</P>
   
   <PRE>
     http://127.0.0.1/
   </PRE>
   
   <P>Once your basic installation is working, you should configure it
  -properly by editing the files in the <SAMP>conf</SAMP> directory.
  -</P>
  +   properly by editing the files in the <SAMP>conf</SAMP> directory.</P>
   
   <P>Because Apache <EM>CANNOT</EM> share the same port with another
  -   TCPIP application, you may need to stop or uninstall certain 
  +   TCP/IP application, you may need to stop or uninstall certain 
      services first.  These include (but are not limited to) other
      web servers, and firewall products such as BlackIce.  If you can
      only start Apache with these services disabled, reconfigure either
      Apache or the other product so that they do not listen on the
  -   same TCPIP ports. You may find the Windows "netstat -an" command useful
  -	 in finding out what ports are in use.
  -</P>
  +   same TCP/IP ports. You may find the Windows "netstat -an" command useful
  +   in finding out what ports are in use.</P>
   
   <H2><A NAME="use">Configuring Apache for Windows</A></H2>
   
  -Apache is configured by files in the <SAMP>conf</SAMP>
  -directory. These are the same as files used to configure the Unix
  -version, but there are a few different directives for Apache on
  -Windows. See the <A HREF="./">Apache documentation</A> for all the
  -available directives.
  +<P>Apache is configured by files in the <SAMP>conf</SAMP>
  +   directory. These are the same as files used to configure the Unix
  +   version, but there are a few different directives for Apache on
  +   Windows. See the <A HREF="./">Apache documentation</A> for all the
  +   available directives.</P>
  +
  +<P>Begin configuring the Apache server by reviewing <CODE>httpd.conf</CODE>

  +   and it's directives.  Although the files <CODE>access.conf</CODE> and
  +   <CODE>srm.conf</CODE> both exist, these are old files which are no longer
  +   used by most administrators, and you will find no directives there.</P>
  +
  +<P><CODE>httpd.conf</CODE> contains a great deal of documentation itself,
  +   followed by the default configuration directives recommended when starting
  +   with the Apache server.  Begin by reading these comments to understand the 
  +   configuration file, and make small changes, starting Apache in a console 
  +   window with each change.  If you make a mistake, it will be easier to back 
  +   up to configuration that last worked.  You will have a better idea of
  +   which change caused the server to fail.</P>
   
  -<P>
  -
  -The main differences in Apache for Windows are:
  +<P>The main differences in Apache for Windows are:</P>
   
   <UL>
     <LI><P>Because Apache for Windows is multithreaded, it does not use a
         separate process for each request, as Apache does with
         Unix. Instead there are usually only two Apache processes running:
         a parent process, and a child which handles the requests. Within
  -      the child each request is handled by a separate thread.
  -      <P>
  -
  -      So the "process"-management directives are different:
  -      <P><A
  -         HREF="mod/core.html#maxrequestsperchild">MaxRequestsPerChild</A>
  +      the child each request is handled by a separate thread.</P>
  +      <P>So the "process"-management directives are different:</P>
  +      <P><A HREF="mod/core.html#maxrequestsperchild">MaxRequestsPerChild</A>
            - Like the Unix directive, this controls how many requests a
              process will serve before exiting. However, unlike Unix, a
              process serves all the requests at once, not just one, so if
              this is set, it is recommended that a very high number is
              used. The recommended default, <CODE>MaxRequestsPerChild
  -           0</CODE>, does not cause the process to ever exit.
  +           0</CODE>, does not cause the process to ever exit.</P>
         <P><A HREF="mod/core.html#threadsperchild">ThreadsPerChild</A>
-
            This directive is new, and tells the server how many threads it
            should use. This is the maximum number of connections the server
  @@ -291,10 +305,10 @@
         uses Unix-style names internally, you must use forward slashes, not
         backslashes. Drive letters can be used; if omitted, the drive with
         the Apache executable will be assumed.</P>
  -  <LI><P>Apache for Windows contains the ability to load modules at runtime,
  +  <LI><P>Apache for Windows has the ability to load modules at runtime,
         without recompiling the server. If Apache is compiled normally, it
         will install a number of optional modules in the
  -      <CODE>\Apache\modules</CODE> directory. To activate these, or other
  +      <CODE>\modules</CODE> directory. To activate these, or other
         modules, the new <A HREF="mod/mod_so.html#loadmodule">LoadModule</A>
         directive must be used. For example, to active the status module,
         use the following (in addition to the status-activating directives
  @@ -363,7 +377,7 @@
   During a binary installation, a registry key will have
   been installed, for example:
   <PRE>
  -  HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3.4\ServerRoot
  +  HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3.13\ServerRoot
   </PRE>
   
   <P>
  @@ -406,20 +420,19 @@
   
   <PRE>
       apache -k shutdown
  -    or
  -    apache -k stop
   </PRE>
  -<BLOCKQUOTE>
  - <STRONG>Note: This option is only available with Apache 1.3.3 and
  - later.  For earlier versions, you need to use Control-C in the
  - Apache console window to shut down the server.</STRONG>
  -</BLOCKQUOTE>
  +<P><STRONG>Note: This option is only available with Apache 1.3.3 and
  +   later.</STRONG></P>
  + <P>For earlier versions, you must use Control-C in the
  +    Apache console window to shut down the server.</P>
  + <P>From version 1.3.3 through 1.3.12, this should be used instead of pressing
  +    Control-C in a running Apache console window, because it allowed Apache 
  +    to end any current transactions and cleanup gracefully.</P>
  + <P>As of version 1.3.13 pressing Control-C in the running window will cleanup 
  +    Apache quite gracefully, and you may use -k stop as an alias for 
  +    -k shutdown.  Earlier versions do not understand -k stop.</P>
   
   <P>
  -This should be used instead of pressing Control-C in a running
  -Apache console window, because it lets Apache end any current
  -transactions and cleanup gracefully. (As of version 1.3.13 pressing
  -Control-C in the running window will also cleanup gracefully).
   
   <P>You can also tell Apache to restart. This makes it re-read the
   configuration files. Any transactions in progress are allowed to
  @@ -429,34 +442,30 @@
   <PRE>
       apache -k restart
   </PRE>
  -<BLOCKQUOTE>
  - <STRONG>Note: This option is only available with Apache 1.3.3 and
  - later.  For earlier versions, you need to use Control-C in the
  - Apache console window to shut down the server.</STRONG>
  -</BLOCKQUOTE>
  +<P><STRONG>Note: This option is only available with Apache 1.3.3 and
  +   later.  For earlier versions, you need to use Control-C in the
  +   Apache console window to shut down the server, and then restart the
  +   server with the Apache command.</STRONG></P>
   
  -<P>Another feature is the configuration files test command.
  -To test the Apache configuration files, run:
  -</P>
  +<P>Another <EM>very useful</EM> feature is the configuration files test
option.
  +   To test the Apache configuration files, run:</P>
   
   <PRE>
       apache -t
   </PRE>
   
   <P>This is especially useful following alterations to the configuration files
  -while Apache is still running. You can make the changes, confirm that the syntax is
  -good by issuing the "apache -t" command, then restart Apache with "apache -k restart".
Apache will
  -re-read the configuration files, allowing any transactions in progress to
  -complete without interruption. Any new request will then be served using the new configuration.
  -</P>
  -
  -
  -<P>
  -Note for people familiar with the Unix version of Apache: these
  -commands provide a Windows equivalent to <CODE>kill -TERM
  -<EM>pid</EM></CODE> and <CODE>kill -USR1 <EM>pid</EM></CODE>.
The command
  -line option used, <CODE>-k</CODE>, was chosen as a reminder of the
  -"kill" command used on Unix.
  +   while Apache is still running. You can make the changes, confirm that the 
  +   syntax is good by issuing the "apache -t" command, then restart Apache with
  +   "apache -k restart". Apache will re-read the configuration files, allowing 
  +   any transactions in progress to complete without interruption. Any new 
  +   request will then be served using the new configuration.</P>
  +
  +<P>Note: for people familiar with the Unix version of Apache, these commands 
  +   provide a Windows equivalent to <CODE>kill -TERM <EM>pid</EM></CODE>
and 
  +   <CODE>kill -USR1 <EM>pid</EM></CODE>. The command line option
used, 
  +   <CODE>-k</CODE>, was chosen as a reminder of the "kill" command used on

  +   Unix.</P>
   
   <!--#include virtual="footer.html" -->
   </BODY>
  
  
  

Mime
View raw message