You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rb...@apache.org on 2001/09/22 21:37:52 UTC

cvs commit: httpd-2.0/docs/manual/platform footer.html header.html perf-hp.html win_compiling.html win_service.html windows.html

rbowen      01/09/22 12:37:52

  Modified:    docs/manual/platform footer.html header.html perf-hp.html
                        win_compiling.html win_service.html windows.html
  Log:
  w3c tidy to convert to xhtml
  
  Revision  Changes    Path
  1.3       +17 -6     httpd-2.0/docs/manual/platform/footer.html
  
  Index: footer.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/platform/footer.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- footer.html	2000/11/24 22:46:50	1.2
  +++ footer.html	2001/09/22 19:37:51	1.3
  @@ -1,8 +1,19 @@
  -<HR>
  +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  +    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   
  -<H3 ALIGN="CENTER">
  - Apache HTTP Server Version 2.0 
  -</H3>
  +<html xmlns="http://www.w3.org/1999/xhtml">
  +  <head>
  +    <meta name="generator" content="HTML Tidy, see www.w3.org" />
   
  -<A HREF="./"><IMG SRC="../images/index.gif" ALT="Index"></A>
  -<A HREF="../"><IMG SRC="../images/home.gif" ALT="Home"></A>
  +    <title></title>
  +  </head>
  +
  +  <body>
  +    <hr />
  +
  +    <h3 align="CENTER">Apache HTTP Server Version 2.0</h3>
  +    <a href="./"><img src="../images/index.gif" alt="Index" /></a>
  +    <a href="../"><img src="../images/home.gif" alt="Home" /></a>
  +  </body>
  +</html>
  +
  
  
  
  1.3       +19 -6     httpd-2.0/docs/manual/platform/header.html
  
  Index: header.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/platform/header.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- header.html	2000/11/24 22:46:50	1.2
  +++ header.html	2001/09/22 19:37:51	1.3
  @@ -1,6 +1,19 @@
  -<DIV ALIGN="CENTER">
  - <IMG SRC="../images/sub.gif" ALT="[APACHE DOCUMENTATION]">
  - <H3>
  -  Apache HTTP Server Version 2.0 
  - </H3>
  -</DIV>
  +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  +    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  +
  +<html xmlns="http://www.w3.org/1999/xhtml">
  +  <head>
  +    <meta name="generator" content="HTML Tidy, see www.w3.org" />
  +
  +    <title></title>
  +  </head>
  +
  +  <body>
  +    <div align="CENTER">
  +      <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> 
  +
  +      <h3>Apache HTTP Server Version 2.0</h3>
  +    </div>
  +  </body>
  +</html>
  +
  
  
  
  1.6       +91 -113   httpd-2.0/docs/manual/platform/perf-hp.html
  
  Index: perf-hp.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/platform/perf-hp.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- perf-hp.html	1998/10/23 07:43:09	1.5
  +++ perf-hp.html	2001/09/22 19:37:51	1.6
  @@ -1,122 +1,100 @@
  -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
  -<HTML>
  -<HEAD>
  -<TITLE>Running a High-Performance Web Server on HPUX</TITLE>
  -</HEAD>
  -
  -<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  -<BODY
  - BGCOLOR="#FFFFFF"
  - TEXT="#000000"
  - LINK="#0000FF"
  - VLINK="#000080"
  - ALINK="#FF0000"
  ->
  -<A NAME="initial">&nbsp;</A>
  -<!--#include virtual="header.html" -->
  +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  +    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   
  -<H1 ALIGN="CENTER">Running a High-Performance Web Server for HPUX</H1>
  -
  -<PRE>
  +<html xmlns="http://www.w3.org/1999/xhtml">
  +  <head>
  +    <meta name="generator" content="HTML Tidy, see www.w3.org" />
  +
  +    <title>Running a High-Performance Web Server on HPUX</title>
  +  </head>
  +  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  +
  +  <body bgcolor="#FFFFFF" text="#000000" link="#0000FF"
  +  vlink="#000080" alink="#FF0000">
  +    <a id="initial" name="initial">&nbsp;</a> 
  +    <!--#include virtual="header.html" -->
  +     
  +
  +    <h1 align="CENTER">Running a High-Performance Web Server for
  +    HPUX</h1>
  +<pre>
   Date: Wed, 05 Nov 1997 16:59:34 -0800
  -From: Rick Jones &lt;<A HREF="mailto:raj@cup.hp.com">raj@cup.hp.com</A>&gt;
  +From: Rick Jones &lt;<a
  +href="mailto:raj@cup.hp.com">raj@cup.hp.com</a>&gt;
   Reply-To: raj@cup.hp.com
   Organization: Network Performance
   Subject: HP-UX tuning tips
  -</PRE>
  -
  -Here are some tuning tips for HP-UX to add to the tuning page.
  -
  -<P>
  -
  -For HP-UX 9.X: Upgrade to 10.20<BR>
  -For HP-UX 10.[00|01|10]: Upgrade to 10.20
  -
  -<P>
  -
  -For HP-UX 10.20: 
  -
  -<P>
  -
  -Install the latest cumulative ARPA Transport Patch. This will allow you
  -to configure the size of the TCP connection lookup hash table. The
  -default is 256 buckets and must be set to a power of two. This is
  -accomplished with adb against the *disc* image of the kernel. The
  -variable name is tcp_hash_size.
  -
  -Notice that it's critically important that you use "W" to write a 32 bit
  -quantity, not "w" to write a 16 bit value when patching the disc image because
  -the tcp_hash_size variable is a 32 bit quantity.
  -
  -<P>
  -
  -How to pick the value? Examine the output of
  -<A HREF="ftp://ftp.cup.hp.com/dist/networking/tools/connhist">
  -ftp://ftp.cup.hp.com/dist/networking/tools/connhist</A> and see how many
  -total TCP connections exist on the system. You probably want that number
  -divided by the hash table size to be reasonably small, say less than 10.
  -Folks can look at HP's SPECweb96 disclosures for some common settings.
  -These can be found at <A HREF="http://www.specbench.org/">
  -http://www.specbench.org/</A>. If an HP-UX system was
  -performing at 1000 SPECweb96 connections per second, the TIME_WAIT time
  -of 60 seconds would mean 60,000 TCP "connections" being tracked. 
  -
  -<P>
  -
  -Folks can check their listen queue depths with
  -<A HREF="ftp://ftp.cup.hp.com/dist/networking/misc/listenq">
  -ftp://ftp.cup.hp.com/dist/networking/misc/listenq</A>.
  -
  -<P>
  -
  -If folks are running Apache on a PA-8000 based system, they should
  -consider "chatr'ing" the Apache executable to have a large page size.
  -This would be "chatr +pi L &lt;BINARY&gt;." The GID of the running executable
  -must have MLOCK privileges. Setprivgrp(1m) should be consulted for
  -assigning MLOCK. The change can be validated by running Glance and
  -examining the memory regions of the server(s) to make sure that they
  -show a non-trivial fraction of the text segment being locked.
  -
  -<P>
  -
  -If folks are running Apache on MP systems, they might consider writing a
  -small program that uses mpctl() to bind processes to processors. A
  -simple pid % numcpu algorithm is probably sufficient. This might even go
  -into the source code.
  -
  -<P>
  -
  -If folks are concerned about the number of FIN_WAIT_2 connections, they
  -can use nettune to shrink the value of tcp_keepstart. However, they
  -should be careful there - certainly do not make it less than oh two to
  -four minutes. If tcp_hash_size has been set well, it is probably OK to
  -let the FIN_WAIT_2's take longer to timeout (perhaps even the default
  -two hours) - they will not on average have a big impact on performance.
  -
  -<P>
  -
  -There are other things that could go into the code base, but that might
  -be left for another email. Feel free to drop me a message if you or
  -others are interested.
  -
  -<P>
  -
  -sincerely,
  -
  -<P>
  -
  -rick jones<BR>
  -<A HREF="http://www.cup.hp.com/netperf/NetperfPage.html">
  -http://www.cup.hp.com/netperf/NetperfPage.html</A>
  -
  -<HR>
  +</pre>
  +    Here are some tuning tips for HP-UX to add to the tuning page. 
   
  -<H3 ALIGN="CENTER">
  - Apache HTTP Server Version 1.3
  -</H3>
  +    <p>For HP-UX 9.X: Upgrade to 10.20<br />
  +     For HP-UX 10.[00|01|10]: Upgrade to 10.20</p>
   
  -<A HREF="./"><IMG SRC="../images/index.gif" ALT="Index"></A>
  -<A HREF="../"><IMG SRC="../images/home.gif" ALT="Home"></A>
  +    <p>For HP-UX 10.20:</p>
   
  -</BODY></HTML>
  +    <p>Install the latest cumulative ARPA Transport Patch. This
  +    will allow you to configure the size of the TCP connection
  +    lookup hash table. The default is 256 buckets and must be set
  +    to a power of two. This is accomplished with adb against the
  +    *disc* image of the kernel. The variable name is tcp_hash_size.
  +    Notice that it's critically important that you use "W" to write
  +    a 32 bit quantity, not "w" to write a 16 bit value when
  +    patching the disc image because the tcp_hash_size variable is a
  +    32 bit quantity.</p>
  +
  +    <p>How to pick the value? Examine the output of <a
  +    href="ftp://ftp.cup.hp.com/dist/networking/tools/connhist">ftp://ftp.cup.hp.com/dist/networking/tools/connhist</a>
  +    and see how many total TCP connections exist on the system. You
  +    probably want that number divided by the hash table size to be
  +    reasonably small, say less than 10. Folks can look at HP's
  +    SPECweb96 disclosures for some common settings. These can be
  +    found at <a
  +    href="http://www.specbench.org/">http://www.specbench.org/</a>.
  +    If an HP-UX system was performing at 1000 SPECweb96 connections
  +    per second, the TIME_WAIT time of 60 seconds would mean 60,000
  +    TCP "connections" being tracked.</p>
  +
  +    <p>Folks can check their listen queue depths with <a
  +    href="ftp://ftp.cup.hp.com/dist/networking/misc/listenq">ftp://ftp.cup.hp.com/dist/networking/misc/listenq</a>.</p>
  +
  +    <p>If folks are running Apache on a PA-8000 based system, they
  +    should consider "chatr'ing" the Apache executable to have a
  +    large page size. This would be "chatr +pi L &lt;BINARY&gt;."
  +    The GID of the running executable must have MLOCK privileges.
  +    Setprivgrp(1m) should be consulted for assigning MLOCK. The
  +    change can be validated by running Glance and examining the
  +    memory regions of the server(s) to make sure that they show a
  +    non-trivial fraction of the text segment being locked.</p>
  +
  +    <p>If folks are running Apache on MP systems, they might
  +    consider writing a small program that uses mpctl() to bind
  +    processes to processors. A simple pid % numcpu algorithm is
  +    probably sufficient. This might even go into the source
  +    code.</p>
  +
  +    <p>If folks are concerned about the number of FIN_WAIT_2
  +    connections, they can use nettune to shrink the value of
  +    tcp_keepstart. However, they should be careful there -
  +    certainly do not make it less than oh two to four minutes. If
  +    tcp_hash_size has been set well, it is probably OK to let the
  +    FIN_WAIT_2's take longer to timeout (perhaps even the default
  +    two hours) - they will not on average have a big impact on
  +    performance.</p>
  +
  +    <p>There are other things that could go into the code base, but
  +    that might be left for another email. Feel free to drop me a
  +    message if you or others are interested.</p>
  +
  +    <p>sincerely,</p>
  +
  +    <p>rick jones<br />
  +     <a
  +    href="http://www.cup.hp.com/netperf/NetperfPage.html">http://www.cup.hp.com/netperf/NetperfPage.html</a></p>
  +    <hr />
  +
  +    <h3 align="CENTER">Apache HTTP Server Version 1.3</h3>
  +    <a href="./"><img src="../images/index.gif" alt="Index" /></a>
  +    <a href="../"><img src="../images/home.gif" alt="Home" /></a>
  +  </body>
  +</html>
   
  
  
  
  1.10      +297 -199  httpd-2.0/docs/manual/platform/win_compiling.html
  
  Index: win_compiling.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/platform/win_compiling.html,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- win_compiling.html	2001/07/23 17:24:47	1.9
  +++ win_compiling.html	2001/09/22 19:37:51	1.10
  @@ -1,223 +1,321 @@
  -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
  -<html>
  -<head>
  -<title>Compiling Apache for Microsoft Windows</title>
  -</head>
  -
  -<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  -<body
  - bgcolor="#FFFFFF"
  - text="#000000"
  - link="#0000FF"
  - vlink="#000080"
  - alink="#FF0000"
  ->
  -<!--#include virtual="header.html" -->
  -
  -<h1 align="center">Compiling Apache for Microsoft Windows</h1>
  -
  -<p>There are many important points before you begin compiling Apache.
  -   See <a href="windows.html">Using Apache with Microsoft Windows</a>
  -   before you begin.</p>
  -
  -<h3><a name="requirements">Requirements</a></h3>
  -
  -<p>Compiling Apache requires the following environment to be properly
  -   installed;
  -
  -<ul>
  -
  -<li>Disk Space<br><br> Make sure you have at least 50 MB of free disk space 
  -    available.  After installation Apache requires approximately 10 MB of disk 
  -    space, plus space for log and cache files, which can grow rapidly.  The 
  -    actual disk space requirements will vary considerably based on your chosen 
  -    configuration and any third-party modules or libraries.<br><br></li>
  -
  -<li>Microsoft Visual C++ 5.0 or higher.<br><br>Apache can be built using
  -    the command line tools, or from within the Visual Studio IDE Workbench.
  -    the command line tools are configured with the vcvars32 batch file:
  +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  +    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  +
  +<html xmlns="http://www.w3.org/1999/xhtml">
  +  <head>
  +    <meta name="generator" content="HTML Tidy, see www.w3.org" />
  +
  +    <title>Compiling Apache for Microsoft Windows</title>
  +  </head>
  +  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  +
  +  <body bgcolor="#FFFFFF" text="#000000" link="#0000FF"
  +  vlink="#000080" alink="#FF0000">
  +    <!--#include virtual="header.html" -->
  +
  +    <h1 align="center">Compiling Apache for Microsoft Windows</h1>
  +
  +    <p>There are many important points before you begin compiling
  +    Apache. See <a href="windows.html">Using Apache with Microsoft
  +    Windows</a> before you begin.</p>
  +
  +    <h3><a id="requirements"
  +    name="requirements">Requirements</a></h3>
  +
  +    <p>Compiling Apache requires the following environment to be
  +    properly installed;</p>
  +
  +    <ul>
  +      <li>Disk Space<br />
  +      <br />
  +       Make sure you have at least 50 MB of free disk space
  +      available. After installation Apache requires approximately
  +      10 MB of disk space, plus space for log and cache files,
  +      which can grow rapidly. The actual disk space requirements
  +      will vary considerably based on your chosen configuration and
  +      any third-party modules or libraries.<br />
  +      <br />
  +      </li>
  +
  +      <li>
  +        Microsoft Visual C++ 5.0 or higher.<br />
  +        <br />
  +         Apache can be built using the command line tools, or from
  +        within the Visual Studio IDE Workbench. the command line
  +        tools are configured with the vcvars32 batch file: 
   <pre>
     "c:\Program Files\DevStudio\VC\Bin\vcvars32.bat"
   </pre>
  +      </li>
   
  -<li>The Windows Platform SDK.<br><br>Visual C++ 5.0 need the updated Microsoft
  -    Windows Platform SDK to enable some Apache features.  For command line 
  -    builds, the Platform SDK environment is prepared by the setenv batch file:
  +      <li>
  +        The Windows Platform SDK.<br />
  +        <br />
  +         Visual C++ 5.0 need the updated Microsoft Windows Platform
  +        SDK to enable some Apache features. For command line
  +        builds, the Platform SDK environment is prepared by the
  +        setenv batch file: 
   <pre>
     "c:\Program Files\Platform SDK\setenv.bat"
   </pre>
  -    The Platform SDK files distributed with Visual C++ 6.0 and later are
  -    sufficient, so those users may skip this requirement.<br><br>
  -
  -    <strong>Note</strong> that the Windows
  -    Platform SDK update is required to enable all supported mod_isapi features.
  -    Without a recent update, Apache will issue warnings under MSVC++ 5.0
  -    that some mod_isapi features will be disabled.  Look for the update at
  -    <a href="http://msdn.microsoft.com/downloads/sdks/platform/platform.asp"
  -    >http://msdn.microsoft.com/downloads/sdks/platform/platform.asp</a>.</p> 
  -
  -<li>The awk utility (awk, gawk or similar.)<br><br>
  -    To install Apache within the build system, several files are modified using
  -    the awk utility.  awk was chosen since it is a very small download (compared
  -    with Perl or WSH/VB) and accomplishes the task. Brian Kernighan's  
  -    <a href="http://cm.bell-labs.com/cm/cs/who/bwk/"
  -    >http://cm.bell-labs.com/cm/cs/who/bwk/</a> site has a compiled native Win32
  -    binary, <a href="http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe"
  -    >http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe</a> 
  -    which you should name awk.exe rather than awk95.exe.<br>
  -    Note that Developer Studio IDE will only find awk.exe from the <u>T</u>ools 
  -    menu <u>O</u>ptions... Directories settings for the Executable files.  Add
  -    the path for awk.exe to this list, as needed.</p>
  -
  -</ul>
  -
  -<h3><a name="commandbuild">Command-Line Build</a></h3>
  -
  -<p>First, unpack the Apache distribution into an appropriate
  -   directory. Open a command-line prompt and cd to that directory.</p>
  -
  -<p>The master Apache makefile instructions are contained in the
  -   <code>Makefile.win</code> file. To compile Apache on Windows NT, simply
  -   use one of the following commands to compiled the release or debug build,
  -   respectively:
  +        The Platform SDK files distributed with Visual C++ 6.0 and
  +        later are sufficient, so those users may skip this
  +        requirement.<br />
  +        <br />
  +         <strong>Note</strong> that the Windows Platform SDK update
  +        is required to enable all supported mod_isapi features.
  +        Without a recent update, Apache will issue warnings under
  +        MSVC++ 5.0 that some mod_isapi features will be disabled.
  +        Look for the update at <a
  +        href="http://msdn.microsoft.com/downloads/sdks/platform/platform.asp">
  +        http://msdn.microsoft.com/downloads/sdks/platform/platform.asp</a>.<br />
  +        <br />
  +      </li>
  +
  +      <li>The awk utility (awk, gawk or similar.)<br />
  +      <br />
  +       To install Apache within the build system, several files are
  +      modified using the awk utility. awk was chosen since it is a
  +      very small download (compared with Perl or WSH/VB) and
  +      accomplishes the task. Brian Kernighan's <a
  +      href="http://cm.bell-labs.com/cm/cs/who/bwk/">http://cm.bell-labs.com/cm/cs/who/bwk/</a>
  +      site has a compiled native Win32 binary, <a
  +      href="http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe">http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe</a>
  +      which you should name awk.exe rather than awk95.exe.<br />
  +       Note that Developer Studio IDE will only find awk.exe from
  +      the <u>T</u>ools menu <u>O</u>ptions... Directories settings
  +      for the Executable files. Add the path for awk.exe to this
  +      list, as needed.<br />
  +      <br />
  +      </li>
  +    </ul>
  +
  +    <h3><a id="commandbuild" name="commandbuild">Command-Line
  +    Build</a></h3>
  +
  +    <p>First, unpack the Apache distribution into an appropriate
  +    directory. Open a command-line prompt and cd to that
  +    directory.</p>
  +
  +    <p>The master Apache makefile instructions are contained in the
  +    <code>Makefile.win</code> file. To compile Apache on Windows
  +    NT, simply use one of the following commands to compiled the
  +    release or debug build, respectively:</p>
   <pre>
       nmake /f Makefile.win _apacher
   
       nmake /f Makefile.win _apached
   </pre>
   
  -<p>Either command will compile Apache. The latter will include debugging
  -   information in the resulting files, making it easier to find bugs and
  -   track down problems.</p>
  -
  -<h3><a name="workspacebuild">Developer Studio Workspace IDE Build</a></h3>
  -
  -<p>Apache can also be compiled using VC++'s VisualStudio development
  -   environment. To simplify this process, a VisualStudio workspace,
  -   Apache.dsw, is provided.  This workspace exposes the entire list of 
  -   working .dsp projects that are required for the complete Apache binary 
  -   release.  It includes dependencies between the projects to assure that 
  -   they are built in the appropriate order.</p>
  -
  -<p>Open the Apache.dsw workspace, and choose InstallBin (Release or Debug
  -   build, as desired) as the Active Project.  InstallBin causes all related
  -   project to be build, and then invokes Makefile.win to move the compiled 
  -   executables and dlls.  You may personalize the INSTDIR= choice by changing 
  -   InstallBin's Settings, General tab, Build command line entry.  INSTDIR 
  -   defaults to the /Apache2 directory.</p>
  -
  -<p>The .dsp project files are distributed in Visual C++ 6.0 format.  Visual
  -   C++ 5.0 (97) will recognize them with the single exception of the /ZI flag
  -   (which corresponds to the VC 5.0 /Zi flag for debugging symbols.)  To quickly
  -   prepare the .dsp files for the Visual Studio 5.0 (97), you can run this command
  -   from the top-level httpd-2.0 directory:
  +    <p>Either command will compile Apache. The latter will include
  +    debugging information in the resulting files, making it easier
  +    to find bugs and track down problems.</p>
  +
  +    <h3><a id="workspacebuild" name="workspacebuild">Developer
  +    Studio Workspace IDE Build</a></h3>
  +
  +    <p>Apache can also be compiled using VC++'s VisualStudio
  +    development environment. To simplify this process, a
  +    VisualStudio workspace, Apache.dsw, is provided. This workspace
  +    exposes the entire list of working .dsp projects that are
  +    required for the complete Apache binary release. It includes
  +    dependencies between the projects to assure that they are built
  +    in the appropriate order.</p>
  +
  +    <p>Open the Apache.dsw workspace, and choose InstallBin
  +    (Release or Debug build, as desired) as the Active Project.
  +    InstallBin causes all related project to be build, and then
  +    invokes Makefile.win to move the compiled executables and dlls.
  +    You may personalize the INSTDIR= choice by changing
  +    InstallBin's Settings, General tab, Build command line entry.
  +    INSTDIR defaults to the /Apache2 directory.</p>
  +
  +    <p>The .dsp project files are distributed in Visual C++ 6.0
  +    format. Visual C++ 5.0 (97) will recognize them with the single
  +    exception of the /ZI flag (which corresponds to the VC 5.0 /Zi
  +    flag for debugging symbols.) To quickly prepare the .dsp files
  +    for the Visual Studio 5.0 (97), you can run this command from
  +    the top-level httpd-2.0 directory:</p>
   <pre>
        perl srclib\apr\build\cvtdsp.pl -5
   </pre>
  -   You must type this command from the <em>top level</em> directory of the httpd
  -   source tree.  Every VC6 .dsp project file within the current directory and 
  -   below will be listed as it is converted.  If you contribute back a patch that
  -   revises project files, please convert them back with the the -6 option instead
  -   of -5, which returns the project files to Visual Studio 6.0 format.</p>
  -
  -<h3><a name="projectcomponents">Project Components</a></h3>
  -
  -<p>The Apache.dsw workspace and makefile.win nmake script both build the
  -   .dsp projects of the Apache server in the following sequence:</p>
  -
  -<ol>
  -   <li><code>srclib\apr\apr.dsp</code>
  -   <li><code>srclib\apr\libapr.dsp</code>
  -   <li><code>srclib\apr-util\uri\gen_uri_delims.dsp</code>
  -   <li><code>srclib\apr-util\aprutil.dsp</code>
  -   <li><code>srclib\apr-util\libaprutil.dsp</code>
  -   <li><code>srclib\pcre\dftables.dsp</code>
  -   <li><code>srclib\pcre\pcre.dsp</code>
  -   <li><code>srclib\pcre\pcreposix.dsp</code>
  -   <li><code>srclib\expat-lite\libexpat.dsp</code>
  -   <li><code>server\gen_test_char.dsp</code>
  -   <li><code>libhttpd.dsp</code>
  -   <li><code>Apache.dsp</code>
  -</ol>
  -
  -   <p>In addition, the <code>os\win32</code> subdirectory contains
  -   project files for the optional modules.</p>
  -
  -<ol>
  -  <li><code>modules\aaa\mod_auth_dbm.dsp</code>
  -  <li><code>modules\aaa\mod_auth_anon.dsp</code>
  -  <li><code>modules\aaa\mod_auth_digest.dsp</code>
  -  <li><code>modules\cache\mod_file_cache.dsp</code>
  -  <li><code>modules\dav\fs\mod_dav_fs.dsp</code>
  -  <li><code>modules\dav\main\mod_dav.dsp</code>
  -  <li><code>modules\generators\mod_info.dsp</code>
  -  <li><code>modules\generators\mod_status.dsp</code>
  -  <li><code>modules\mappers\mod_rewrite.dsp</code>
  -  <li><code>modules\mappers\mod_speling.dsp</code>
  -  <li><code>modules\metadata\mod_usertrack.dsp</code>
  -  <li><code>modules\metadata\mod_cern_meta.dsp</code>
  -  <li><code>modules\metadata\mod_headers.dsp</code>
  -  <li><code>modules\metadata\mod_expires.dsp</code>
  -  <li><code>modules\ssl\mod_ssl.dsp</code>
  -  <li><code>modules\tls\mod_tls.dsp</code>
  -</ol>
  -
  -<p>The <code>support\</code> folder contains project files for additional
  -   programs that are not part of the Apache runtime, but are used by
  -   the administrator to test Apache and maintain password and log files.</p>
  -
  -<ol>
  -  <li><code>support\ab.dsp</code>
  -  <li><code>support\htdigest.dsp</code>
  -  <li><code>support\htpasswd.dsp</code>
  -  <li><code>support\logresolve.dsp</code>
  -  <li><code>support\rotatelogs.dsp</code>
  -  <li><code>support\win32\wintty.dsp</code>
  -</ol>
  -
  -<p>Once Apache has been compiled, it needs to be installed in its server
  -   root directory. The default is the <code>\Apache2</code>
  -   directory, of the same drive.</p>
  +    You must type this command from the <em>top level</em>
  +    directory of the httpd source tree. Every VC6 .dsp project file
  +    within the current directory and below will be listed as it is
  +    converted. If you contribute back a patch that revises project
  +    files, please convert them back with the the -6 option instead
  +    of -5, which returns the project files to Visual Studio 6.0
  +    format.<br />
  +     <br />
  +     
  +
  +    <h3><a id="projectcomponents" name="projectcomponents">Project
  +    Components</a></h3>
  +
  +    <p>The Apache.dsw workspace and makefile.win nmake script both
  +    build the .dsp projects of the Apache server in the following
  +    sequence:</p>
  +
  +    <ol>
  +      <li><code>srclib\apr\apr.dsp</code></li>
  +
  +      <li><code>srclib\apr\libapr.dsp</code></li>
  +
  +      <li><code>srclib\apr-util\uri\gen_uri_delims.dsp</code></li>
  +
  +      <li><code>srclib\apr-util\aprutil.dsp</code></li>
  +
  +      <li><code>srclib\apr-util\libaprutil.dsp</code></li>
  +
  +      <li><code>srclib\pcre\dftables.dsp</code></li>
  +
  +      <li><code>srclib\pcre\pcre.dsp</code></li>
  +
  +      <li><code>srclib\pcre\pcreposix.dsp</code></li>
  +
  +      <li><code>srclib\expat-lite\libexpat.dsp</code></li>
  +
  +      <li><code>server\gen_test_char.dsp</code></li>
  +
  +      <li><code>libhttpd.dsp</code></li>
  +
  +      <li><code>Apache.dsp</code></li>
  +    </ol>
  +
  +    <p>In addition, the <code>os\win32</code> subdirectory contains
  +    project files for the optional modules.</p>
  +
  +    <ol>
  +      <li><code>modules\aaa\mod_auth_dbm.dsp</code></li>
  +
  +      <li><code>modules\aaa\mod_auth_anon.dsp</code></li>
  +
  +      <li><code>modules\aaa\mod_auth_digest.dsp</code></li>
  +
  +      <li><code>modules\cache\mod_file_cache.dsp</code></li>
  +
  +      <li><code>modules\dav\fs\mod_dav_fs.dsp</code></li>
  +
  +      <li><code>modules\dav\main\mod_dav.dsp</code></li>
  +
  +      <li><code>modules\generators\mod_info.dsp</code></li>
  +
  +      <li><code>modules\generators\mod_status.dsp</code></li>
  +
  +      <li><code>modules\mappers\mod_rewrite.dsp</code></li>
  +
  +      <li><code>modules\mappers\mod_speling.dsp</code></li>
  +
  +      <li><code>modules\metadata\mod_usertrack.dsp</code></li>
  +
  +      <li><code>modules\metadata\mod_cern_meta.dsp</code></li>
   
  -<p>To build and install all the files into the desired folder <em>dir</em>
  -   automatically, use one the following nmake commands:
  +      <li><code>modules\metadata\mod_headers.dsp</code></li>
  +
  +      <li><code>modules\metadata\mod_expires.dsp</code></li>
  +
  +      <li><code>modules\ssl\mod_ssl.dsp</code></li>
  +
  +      <li><code>modules\tls\mod_tls.dsp</code></li>
  +    </ol>
  +
  +    <p>The <code>support\</code> folder contains project files for
  +    additional programs that are not part of the Apache runtime,
  +    but are used by the administrator to test Apache and maintain
  +    password and log files.</p>
  +
  +    <ol>
  +      <li><code>support\ab.dsp</code></li>
  +
  +      <li><code>support\htdigest.dsp</code></li>
  +
  +      <li><code>support\htpasswd.dsp</code></li>
  +
  +      <li><code>support\logresolve.dsp</code></li>
  +
  +      <li><code>support\rotatelogs.dsp</code></li>
  +
  +      <li><code>support\win32\wintty.dsp</code></li>
  +    </ol>
  +
  +    <p>Once Apache has been compiled, it needs to be installed in
  +    its server root directory. The default is the
  +    <code>\Apache2</code> directory, of the same drive.</p>
  +
  +    <p>To build and install all the files into the desired folder
  +    <em>dir</em> automatically, use one the following nmake
  +    commands:</p>
   <pre>
       nmake /f Makefile.win installr INSTDIR=<em>dir</em>
   
       nmake /f Makefile.win installd INSTDIR=<em>dir</em>
   </pre>
  -   The <em>dir</em> argument to INSTDIR gives the installation directory; it 
  -   can be omitted if Apache is to be installed into <samp>\Apache2</samp>.</p>
  +    The <em>dir</em> argument to INSTDIR gives the installation
  +    directory; it can be omitted if Apache is to be installed into
  +    <samp>\Apache2</samp>.<br />
  +     <br />
  +     
  +
  +    <p>This will install the following:</p>
  +
  +    <ul>
  +      <li><code><em>dir</em>\bin\Apache.exe</code> - Apache
  +      executable</li>
  +
  +      <li><code><em>dir</em>\bin\htdigest.exe</code> - Digest auth
  +      password file utility</li>
  +
  +      <li><code><em>dir</em>\bin\htpasswd.exe</code> - Basic auth
  +      password file utility</li>
  +
  +      <li><code><em>dir</em>\bin\logresolve.exe</code> - Log file
  +      dns name lookup utility</li>
  +
  +      <li><code><em>dir</em>\bin\rotatelogs.exe</code> - Log file
  +      cycling utility</li>
  +
  +      <li><code><em>dir</em>\bin\wintty.exe</code> - Console window
  +      utility</li>
  +
  +      <li><code><em>dir</em>\bin\libapr.dll</code> - Apache
  +      Portable Runtime shared library</li>
  +
  +      <li><code><em>dir</em>\bin\libaprutil.dll</code> - Apache
  +      Utility Runtime shared library</li>
  +
  +      <li><code><em>dir</em>\bin\libhttpd.dll</code> - Apache Core
  +      library</li>
  +
  +      <li><code><em>dir</em>\modules\mod_*.so</code> - Loadable
  +      Apache modules</li>
  +
  +      <li><code><em>dir</em>\conf</code> - Configuration
  +      directory</li>
  +
  +      <li><code><em>dir</em>\logs</code> - Empty logging
  +      directory</li>
  +
  +      <li><code><em>dir</em>\include</code> - C language header
  +      files</li>
  +
  +      <li><code><em>dir</em>\lib</code> - Static Link library
  +      files</li>
  +
  +      <li><code><em>dir</em>\libexec</code> - DLL link library
  +      files</li>
  +    </ul>
  +
  +    <p><strong>Warning about building Apache from the development
  +    tree</strong></p>
   
  -<p>This will install the following:</p>
  +    <p>Only the .dsp files are maintained between release builds.
  +    The .mak files are NOT regenerated, due to the tremendous waste
  +    of reviewer's time. Therefore, you cannot rely on the NMAKE
  +    commands above to build revised .dsp project files unless you
  +    then export all .mak files yourself from the project. This is
  +    unnecessary if you build from within the Microsoft
  +    DeveloperStudio environment.</p>
  +    <!--#include virtual="footer.html" -->
  +  </body>
  +</html>
   
  -<ul>
  -  <li><code><em>dir</em>\bin\Apache.exe</code> - Apache executable
  -  <li><code><em>dir</em>\bin\htdigest.exe</code> - Digest auth password file utility
  -  <li><code><em>dir</em>\bin\htpasswd.exe</code> - Basic auth password file utility
  -  <li><code><em>dir</em>\bin\logresolve.exe</code> - Log file dns name lookup utility
  -  <li><code><em>dir</em>\bin\rotatelogs.exe</code> - Log file cycling utility
  -  <li><code><em>dir</em>\bin\wintty.exe</code> - Console window utility
  -  <li><code><em>dir</em>\bin\libapr.dll</code> - Apache Portable Runtime shared library
  -  <li><code><em>dir</em>\bin\libaprutil.dll</code> - Apache Utility Runtime shared library
  -  <li><code><em>dir</em>\bin\libhttpd.dll</code> - Apache Core library
  -  <li><code><em>dir</em>\modules\mod_*.so</code> - Loadable Apache modules
  -  <li><code><em>dir</em>\conf</code> - Configuration directory
  -  <li><code><em>dir</em>\logs</code> - Empty logging directory
  -  <li><code><em>dir</em>\include</code> - C language header files
  -  <li><code><em>dir</em>\lib</code> - Static Link library files
  -  <li><code><em>dir</em>\libexec</code> - DLL link library files
  -</ul>
  -
  -<p><strong>Warning about building Apache from the development tree</strong></p>
  -
  -<p>Only the .dsp files are maintained between release builds.  The
  -   .mak files are NOT regenerated, due to the tremendous waste of
  -   reviewer's time.  Therefore, you cannot rely on the NMAKE commands 
  -   above to build revised .dsp project files unless you then export
  -   all .mak files yourself from the project.  This is unnecessary if 
  -   you build from within the Microsoft DeveloperStudio environment.</p>   
  -
  -<!--#include virtual="footer.html" -->
  -</body>
  -</body>
  
  
  
  1.5       +319 -275  httpd-2.0/docs/manual/platform/win_service.html
  
  Index: win_service.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/platform/win_service.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- win_service.html	2001/02/28 04:41:24	1.4
  +++ win_service.html	2001/09/22 19:37:51	1.5
  @@ -1,325 +1,369 @@
  -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
  -<HTML>
  -<HEAD>
  -<TITLE>Running Apache for Windows as a Service</TITLE>
  -</HEAD>
  -
  -<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  -<BODY
  - BGCOLOR="#FFFFFF"
  - TEXT="#000000"
  - LINK="#0000FF"
  - VLINK="#000080"
  - ALINK="#FF0000"
  ->
  -<!--#include virtual="header.html" -->
  -
  -<H1 ALIGN="CENTER">Running Apache for Windows as a Service</H1>
  -
  -<P>Apache can be run as a service on Windows NT/2000.  (There is also some 
  -   HIGHLY EXPERIMENTAL support for similar behavior on 
  -   <a href="#win95svc">Windows 95/98</a>, introduced with Apache 1.3.13).</P>
  -
  -<P>Installing Apache as a service should only be done once you can 
  -   successfully run it in a console window. See 
  -   <A HREF="windows.html">Using Apache with Microsoft Windows</A>
  -   before you attempt to install or run Apache as a service. Changes to the 
  -   httpd.conf file should always be followed by starting Apache as a console 
  -   window.  If this succeeds, the service should succeed.</P>
  -
  -<P><STRONG>NOTE: Prior to version 1.3.13, the configuration was <EM>not 
  -   tested</EM> prior to performing the installation</STRONG>, and a lack of 
  -   service dependencies often caused the console window to succeed, but the
  -   service would still fail.  See <A HREF="#service">below</A> if you are 
  -   having problems running a version of Apache prior to 1.3.13 to resolve the 
  -   issue.  If you have this problem with version 1.3.13 or greater, first try 
  -   uninstalling (-u) and re-installing (-i) the Apache service.</P>
  -
  -<HR>
  -
  -<P>To start Apache as a service, you first need to install it as a
  -   service. Multiple Apache services can be installed, each with a
  -   different name and configuration.  To install the default Apache
  -   service named "Apache", run the "Install Apache as Service (NT only)"
  -   option from the Start menu. Once this is done you can start the "Apache"
  -   service by opening the Services window (in the Control Panel), selecting 
  -   Apache, then clicking on Start. Apache will now be running, hidden in the 
  -   background. You can later stop Apache by clicking on Stop. As an 
  -   alternative to using the Services window, you can start and stop the 
  -   "Apache" service from the command line with</P>
  +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  +    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   
  -<PRE>
  +<html xmlns="http://www.w3.org/1999/xhtml">
  +  <head>
  +    <meta name="generator" content="HTML Tidy, see www.w3.org" />
  +
  +    <title>Running Apache for Windows as a Service</title>
  +  </head>
  +  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  +
  +  <body bgcolor="#FFFFFF" text="#000000" link="#0000FF"
  +  vlink="#000080" alink="#FF0000">
  +    <!--#include virtual="header.html" -->
  +
  +    <h1 align="CENTER">Running Apache for Windows as a Service</h1>
  +
  +    <p>Apache can be run as a service on Windows NT/2000. (There is
  +    also some HIGHLY EXPERIMENTAL support for similar behavior on
  +    <a href="#win95svc">Windows 95/98</a>, introduced with Apache
  +    1.3.13).</p>
  +
  +    <p>Installing Apache as a service should only be done once you
  +    can successfully run it in a console window. See <a
  +    href="windows.html">Using Apache with Microsoft Windows</a>
  +    before you attempt to install or run Apache as a service.
  +    Changes to the httpd.conf file should always be followed by
  +    starting Apache as a console window. If this succeeds, the
  +    service should succeed.</p>
  +
  +    <p><strong>NOTE: Prior to version 1.3.13, the configuration was
  +    <em>not tested</em> prior to performing the
  +    installation</strong>, and a lack of service dependencies often
  +    caused the console window to succeed, but the service would
  +    still fail. See <a href="#service">below</a> if you are having
  +    problems running a version of Apache prior to 1.3.13 to resolve
  +    the issue. If you have this problem with version 1.3.13 or
  +    greater, first try uninstalling (-u) and re-installing (-i) the
  +    Apache service.</p>
  +    <hr />
  +
  +    <p>To start Apache as a service, you first need to install it
  +    as a service. Multiple Apache services can be installed, each
  +    with a different name and configuration. To install the default
  +    Apache service named "Apache", run the "Install Apache as
  +    Service (NT only)" option from the Start menu. Once this is
  +    done you can start the "Apache" service by opening the Services
  +    window (in the Control Panel), selecting Apache, then clicking
  +    on Start. Apache will now be running, hidden in the background.
  +    You can later stop Apache by clicking on Stop. As an
  +    alternative to using the Services window, you can start and
  +    stop the "Apache" service from the command line with</p>
  +<pre>
     NET START APACHE
     NET STOP APACHE
  -</PRE>
  +</pre>
   
  -<P>See <A HREF="#signal">Controlling Apache as a Service</A>
  -   for more information on installing and controlling Apache services.</P>
  -
  -<P><STRONG>Apache, unlike many other Windows NT/2000 services, logs any
  -   errors to it's own error.log file in the logs folder within the
  -   Apache server root folder.  You will <EM>not</EM> find Apache error 
  -   details in the Windows NT Event Log.</STRONG></P>
  -
  -<P>After starting Apache as a service (or if you have trouble starting it) 
  -   you can test it using the same <A HREF="windows.html#cmdline">procedure</a>
  -   as for running in a console window.  Remember to use the command:</P>
  -
  -<PRE>
  +    <p>See <a href="#signal">Controlling Apache as a Service</a>
  +    for more information on installing and controlling Apache
  +    services.</p>
  +
  +    <p><strong>Apache, unlike many other Windows NT/2000 services,
  +    logs any errors to it's own error.log file in the logs folder
  +    within the Apache server root folder. You will <em>not</em>
  +    find Apache error details in the Windows NT Event
  +    Log.</strong></p>
  +
  +    <p>After starting Apache as a service (or if you have trouble
  +    starting it) you can test it using the same <a
  +    href="windows.html#cmdline">procedure</a> as for running in a
  +    console window. Remember to use the command:</p>
  +<pre>
     apache -n "service name"
  -</PRE>
  +</pre>
   
  -<P>to assure you are using the service's configuration.</P>
  -	 
  -	 
  -<H2><A NAME="service">Running Apache for Windows as a Service</A></H2>
  +    <p>to assure you are using the service's configuration.</p>
   
  -<P><STRONG>Note: The -n option to specify a service name is only available
  -   with Apache 1.3.7 and later.</STRONG>  Earlier versions of Apache only 
  -   support the default service name 'Apache'.</P>
  +    <h2><a id="service" name="service">Running Apache for Windows
  +    as a Service</a></h2>
   
  -<P>You can install Apache as a Windows NT service as follows:</P>
  +    <p><strong>Note: The -n option to specify a service name is
  +    only available with Apache 1.3.7 and later.</strong> Earlier
  +    versions of Apache only support the default service name
  +    'Apache'.</p>
   
  -<PRE>
  +    <p>You can install Apache as a Windows NT service as
  +    follows:</p>
  +<pre>
       apache -i -n "service name"
  -</PRE>
  +</pre>
   
  -<P>To install a service to use a particular configuration, specify the
  -   configuration file when the service is installed:</P>
  -
  -<PRE>
  +    <p>To install a service to use a particular configuration,
  +    specify the configuration file when the service is
  +    installed:</p>
  +<pre>
       apache -i -n "service name" -f "\my server\conf\my.conf"
  -</PRE>
  -
  -<P>To remove an Apache service, use:</P>
  +</pre>
   
  -<PRE>
  +    <p>To remove an Apache service, use:</p>
  +<pre>
       apache -u -n "service name"
  -</PRE>
  +</pre>
   
  -<P>The default "service name", if one is not specified, is "Apache".</P>
  +    <p>The default "service name", if one is not specified, is
  +    "Apache".</p>
   
  -<P>Once a service is installed, you can use the <SAMP>-n</SAMP> option, in 
  -   conjunction with other options, to refer to a service's configuration file.
  -   For example:</P>
  +    <p>Once a service is installed, you can use the <samp>-n</samp>
  +    option, in conjunction with other options, to refer to a
  +    service's configuration file. For example:</p>
   
  -<P>To test a service's configuration file:</P>
  -<PRE>
  +    <p>To test a service's configuration file:</p>
  +<pre>
       apache -n "service name" -t
  -</PRE>
  +</pre>
   
  -<P>To start a console Apache using a service's configuration file:</P>
  -<PRE>
  +    <p>To start a console Apache using a service's configuration
  +    file:</p>
  +<pre>
       apache -n "service name"
  -</PRE>
  -
  -<H2><A NAME="depends">Important Note on service dependencies:</A></H2>
  +</pre>
   
  -<P>Prior to Apache release 1.3.13, the dependencies required to
  -   successfully start an installed service were not configured.
  -   After installing a service using earlier versions of Apache, 
  -   you must follow these steps:
  +    <h2><a id="depends" name="depends">Important Note on service
  +    dependencies:</a></h2>
   
  -<PRE>
  +    <p>Prior to Apache release 1.3.13, the dependencies required to
  +    successfully start an installed service were not configured.
  +    After installing a service using earlier versions of Apache,
  +    you must follow these steps:</p>
  +<pre>
       Run regedt32
  -    Select <U>W</U>indow - "HKEY_LOCAL_MACHINE on Local Machine" from the menu
  +    Select <u>W</u>indow - "HKEY_LOCAL_MACHINE on Local Machine" from the menu
       Double-click to open the SYSTEM, then the CurrentControlSet keys
       Scroll down and click on the Apache servicename
  -    Select <U>E</U>dit - Add <U>V</U>alue... from the menu
  +    Select <u>E</u>dit - Add <u>V</u>alue... from the menu
       Fill in the Add Value dialog with 
  -        <U>V</U>alue Name: DependOnGroup 
  -        <U>D</U>ata Type: REG_MULTI_SZ
  +        <u>V</u>alue Name: DependOnGroup 
  +        <u>D</u>ata Type: REG_MULTI_SZ
           and click OK
       Leave the Multi-String Editor dialog empty and click OK
  -    Select <U>E</U>dit - Add <U>V</U>alue... from the menu
  +    Select <u>E</u>dit - Add <u>V</u>alue... from the menu
       Fill in the Add Value dialog with 
  -        <U>V</U>alue Name: DependOnService
  -        <U>D</U>ata Type: REG_MULTI_SZ
  +        <u>V</u>alue Name: DependOnService
  +        <u>D</u>ata Type: REG_MULTI_SZ
           and click OK
       Type the following list (one per line) in the Multi-String Editor dialog
           Tcpip
           Afd
           and click OK
  -</PRE>
  +</pre>
   
  -<P>If you are using COM or DCOM components from a third party module, ISAPI,
  -   or other add-in scripting technologies such as ActiveState Perl, you may
  -   also need to add the entry Rpcss to the DependOnService list.  To avoid
  -   exposing the TCP port 135 when it is unnecessary, Apache does not create
  -   that entry upon installation.  Follow the directions above to find or 
  -   create the DependOnService value, double click that value if it already 
  -   exists, and add the Rpcss entry to the list.</P>
  -
  -
  -<H2>User Account for Apache Service to Run As (NT/2000)</H2>
  -
  -<P>When Apache is first installed as a service (e.g. with the -i option)
  -   it will run as user "System" (the LocalSystem account).  There should
  -   be few issues if all resources for the web server reside on the local
  -   system, but it has broad security privilages to affect the local machine!</P>
  -
  -<BLOCKQUOTE>
  -       LocalSystem is a very privileged account locally, so 
  -       you shouldn't run any shareware applications there. 
  -       However, it has no network privileges and cannot leave 
  -       the machine via any NT-secured mechanism, including
  -       file system, named pipes, DCOM, or secure RPC.
  -</BLOCKQUOTE> 
  -
  -<P><STRONG>NEVER grant network privilages to the SYSTEM account!</STRONG>
  -   Create a new user account instead, grant the appropriate privilages to
  -   that user, and use the the 'Log On As:' option.  Select the Start Menu -&gt;
  -   Settings -&gt; Control Panel -&gt; Services -&gt; apache service ... and click 
  -   the "Startup" button to access this setting.</P>
  -
  -<BLOCKQUOTE>
  -       A service that runs in the context of the LocalSystem account
  -       inherits the security context of the SCM. It is not associated with 
  -       any logged-on user account and does not have credentials (domain name,
  -       user name, and password) to be used for verification. 
  -</BLOCKQUOTE>
  -
  -<P>The SYSTEM account has no privilages to the network, so shared pages or
  -   a shared installation of Apache is invisible to the service.  If you intend
  -   to use <EM>any</EM> network resources, the following steps should help:</P>
  -
  -<UL>
  -<LI>Select Apache from the Control Panel's Service dialog and click Startup.
  -<LI>Verify that the service account is correct.  You may wish to create an 
  -    account for your Apache services.
  -<LI>Retype the password and password confirmation.
  -<LI>Go to User Manager for Domains.
  -<LI>Click on Policies from the title bar menu, and select User Rights.
  -<LI>Select the option for Advanced User Rights.
  -<LI>In the drop-down list, verify that the following rights have been 
  -    granted to the selected account:
  -    <UL>
  -        <LI>Act as part of the operating system
  -        <LI>Back up files and directories
  -        <LI>Log on as a service
  -        <LI>Restore files and directories
  -    </UL>
  -<LI>Confirm that the selected account is a member of the Users group.
  -<LI>Confirm the selected account has access to all document and script 
  -    directories (minimally read and browse access).
  -<LI>Confirm the selected account has read/write/delete access to the Apache 
  -    logs directory!
  -</UL>
  -
  -<P>If you allow the account to log in as a user, then you can log in yourself
  -   and test that the account has the privilages to execute the scripts, read
  -   the web pages, and that you can start Apache in a console window.  If this
  -   works, and you have followed the steps above, Apache should execute as
  -   a service with no problems.</P>
  -<P><STRONG>Note: error code 2186</STRONG> is a good indication that you need 
  -   to review the 'Log On As' configuration, since the server can't access a 
  -   required network resource.</P>
  -
  -
  -<H2><A NAME="trouble">Troubleshooting Apache for Windows as a Service</A></H2>
  -
  -<P>When starting Apache as a service you may encounter an error message from
  -  Windows service manager. For example if you try to start Apache using the Services
  -  applet in Windows Control Panel you may get the following message;
  -<PRE>
  +    <p>If you are using COM or DCOM components from a third party
  +    module, ISAPI, or other add-in scripting technologies such as
  +    ActiveState Perl, you may also need to add the entry Rpcss to
  +    the DependOnService list. To avoid exposing the TCP port 135
  +    when it is unnecessary, Apache does not create that entry upon
  +    installation. Follow the directions above to find or create the
  +    DependOnService value, double click that value if it already
  +    exists, and add the Rpcss entry to the list.</p>
  +
  +    <h2>User Account for Apache Service to Run As (NT/2000)</h2>
  +
  +    <p>When Apache is first installed as a service (e.g. with the
  +    -i option) it will run as user "System" (the LocalSystem
  +    account). There should be few issues if all resources for the
  +    web server reside on the local system, but it has broad
  +    security privilages to affect the local machine!</p>
  +
  +    <blockquote>
  +      LocalSystem is a very privileged account locally, so you
  +      shouldn't run any shareware applications there. However, it
  +      has no network privileges and cannot leave the machine via
  +      any NT-secured mechanism, including file system, named pipes,
  +      DCOM, or secure RPC.
  +    </blockquote>
  +
  +    <p><strong>NEVER grant network privilages to the SYSTEM
  +    account!</strong> Create a new user account instead, grant the
  +    appropriate privilages to that user, and use the the 'Log On
  +    As:' option. Select the Start Menu -&gt; Settings -&gt; Control
  +    Panel -&gt; Services -&gt; apache service ... and click the
  +    "Startup" button to access this setting.</p>
  +
  +    <blockquote>
  +      A service that runs in the context of the LocalSystem account
  +      inherits the security context of the SCM. It is not
  +      associated with any logged-on user account and does not have
  +      credentials (domain name, user name, and password) to be used
  +      for verification.
  +    </blockquote>
  +
  +    <p>The SYSTEM account has no privilages to the network, so
  +    shared pages or a shared installation of Apache is invisible to
  +    the service. If you intend to use <em>any</em> network
  +    resources, the following steps should help:</p>
  +
  +    <ul>
  +      <li>Select Apache from the Control Panel's Service dialog and
  +      click Startup.</li>
  +
  +      <li>Verify that the service account is correct. You may wish
  +      to create an account for your Apache services.</li>
  +
  +      <li>Retype the password and password confirmation.</li>
  +
  +      <li>Go to User Manager for Domains.</li>
  +
  +      <li>Click on Policies from the title bar menu, and select
  +      User Rights.</li>
  +
  +      <li>Select the option for Advanced User Rights.</li>
  +
  +      <li>
  +        In the drop-down list, verify that the following rights
  +        have been granted to the selected account: 
  +
  +        <ul>
  +          <li>Act as part of the operating system</li>
  +
  +          <li>Back up files and directories</li>
  +
  +          <li>Log on as a service</li>
  +
  +          <li>Restore files and directories</li>
  +        </ul>
  +      </li>
  +
  +      <li>Confirm that the selected account is a member of the
  +      Users group.</li>
  +
  +      <li>Confirm the selected account has access to all document
  +      and script directories (minimally read and browse
  +      access).</li>
  +
  +      <li>Confirm the selected account has read/write/delete access
  +      to the Apache logs directory!</li>
  +    </ul>
  +
  +    <p>If you allow the account to log in as a user, then you can
  +    log in yourself and test that the account has the privilages to
  +    execute the scripts, read the web pages, and that you can start
  +    Apache in a console window. If this works, and you have
  +    followed the steps above, Apache should execute as a service
  +    with no problems.</p>
  +
  +    <p><strong>Note: error code 2186</strong> is a good indication
  +    that you need to review the 'Log On As' configuration, since
  +    the server can't access a required network resource.</p>
  +
  +    <h2><a id="trouble" name="trouble">Troubleshooting Apache for
  +    Windows as a Service</a></h2>
  +
  +    <p>When starting Apache as a service you may encounter an error
  +    message from Windows service manager. For example if you try to
  +    start Apache using the Services applet in Windows Control Panel
  +    you may get the following message;</p>
  +<pre>
     Could not start the apache service on \\COMPUTER
     Error 1067; The process terminated unexpectedly.
  -</PRE>
  -<P>You will get this error if there is any problem starting Apache. In order to see
  -   what is causing the problem you should follow the instructions
  -   for <a href="windows.html#cmdline">Running Apache for Windows from the Command Line</a>.</P>
  -
  -<P>Also, Apache 1.3.13 now records startup errors in the Application Event Log
  -   under Windows NT/2000, if Apache is run as a service.  Run the Event Viewer
  -   and select <U>L</U>og ... <U>A</U>pplication to see these events.
  -
  -<P><STRONG>Check the Application Event Log with the Event Viewer in case of any
  -   problems, even if no error message pops up to warn you that an error 
  -   occured.</STRONG></P>
  -
  -<H2><A NAME="cmdline">Running Apache for Windows from the Command Line</A></H2>
  -
  -For details on controlling Apache service from the command line, please refer to
  -<a href="windows.html#cmdline">console command line</a> section.
  -
  +</pre>
   
  -<H2><A NAME="signal">Controlling Apache as a Service</A></H2>
  -
  -<P>Multiple instances of Apache can be installed and run as services. Signal 
  -   an installed Apache service to start, restart, or shutdown/stop 
  -   as follows:</P>
  -
  -<PRE>
  +    <p>You will get this error if there is any problem starting
  +    Apache. In order to see what is causing the problem you should
  +    follow the instructions for <a
  +    href="windows.html#cmdline">Running Apache for Windows from the
  +    Command Line</a>.</p>
  +
  +    <p>Also, Apache 1.3.13 now records startup errors in the
  +    Application Event Log under Windows NT/2000, if Apache is run
  +    as a service. Run the Event Viewer and select <u>L</u>og ...
  +    <u>A</u>pplication to see these events.</p>
  +
  +    <p><strong>Check the Application Event Log with the Event
  +    Viewer in case of any problems, even if no error message pops
  +    up to warn you that an error occured.</strong></p>
  +
  +    <h2><a id="cmdline" name="cmdline">Running Apache for Windows
  +    from the Command Line</a></h2>
  +    For details on controlling Apache service from the command
  +    line, please refer to <a href="windows.html#cmdline">console
  +    command line</a> section. 
  +
  +    <h2><a id="signal" name="signal">Controlling Apache as a
  +    Service</a></h2>
  +
  +    <p>Multiple instances of Apache can be installed and run as
  +    services. Signal an installed Apache service to start, restart,
  +    or shutdown/stop as follows:</p>
  +<pre>
       apache -n "service name" -k start
       apache -n "service name" -k restart
       apache -n "service name" -k shutdown
       apache -n "service name" -k stop
  -</PRE>
  -
  -<P>For the default "Apache" service, the -n Apache option is still required, 
  -   since the -k commands without the -n option are directed at Apache running 
  -   in a  console window.  The quotes are only required if the service name 
  -   contains spaces.</P>
  -
  -<P><STRONG>Note: the -k stop alias for the -k shutdown command was introduced
  -   in Apache version 1.3.13.</STRONG>  Earlier versions of Apache will only
  -   recognize the -k shutdown option.  Prior to 1.3.3, Apache did not recognize
  -   <EM>any</EM> -k options at all!</P>
  +</pre>
   
  -<P>In addition, you can use the native NT NET command to
  -   start and stop Apache services as follows:</P>
  -
  -<PRE>
  +    <p>For the default "Apache" service, the -n Apache option is
  +    still required, since the -k commands without the -n option are
  +    directed at Apache running in a console window. The quotes are
  +    only required if the service name contains spaces.</p>
  +
  +    <p><strong>Note: the -k stop alias for the -k shutdown command
  +    was introduced in Apache version 1.3.13.</strong> Earlier
  +    versions of Apache will only recognize the -k shutdown option.
  +    Prior to 1.3.3, Apache did not recognize <em>any</em> -k
  +    options at all!</p>
  +
  +    <p>In addition, you can use the native NT NET command to start
  +    and stop Apache services as follows:</p>
  +<pre>
       NET START "service name"
       NET STOP "service name"
  -</PRE>
  -
  -<P>Again, quotes are only required if the service name contains spaces.</P>
  +</pre>
   
  -<H2><A NAME="win95svc">HIGHLY EXPERIMENTAL Windows 95/98 Service</A></H2>
  +    <p>Again, quotes are only required if the service name contains
  +    spaces.</p>
   
  -<P><STRONG>Note: The service options for Windows 95 and 98 are only available
  -   with Apache 1.3.13 and later.</STRONG>  Earlier versions of Apache only 
  -   supported Apache in a console window for Windows 95/98.</P>
  +    <h2><a id="win95svc" name="win95svc">HIGHLY EXPERIMENTAL
  +    Windows 95/98 Service</a></h2>
   
  -<P>There is some support for Apache on Windows 95/98 to behave in a similar
  -   manner as a service on Windows NT/2000. It is <EM>highly experimental</EM>,
  -   if it works (at all) the Apache Sofware Foundation will not attest to it's 
  -   reliability or future support. Proceed at your own risk!</P>
  -
  -<P>Once you have confirmed that Apache runs correctly at the
  -   <a href="windows.html#cmdline">Command Prompt</a> you can install, control
  -   and uninstall it with the same commands as the Windows NT/2000 version.</P>
  -
  -<P>There are, however, significant differences that you should note:</P>
  -
  -<P>Apache will attempt to start and if successful it will run in the 
  -   background.  If you run the command</p>
  -
  -<PRE>
  +    <p><strong>Note: The service options for Windows 95 and 98 are
  +    only available with Apache 1.3.13 and later.</strong> Earlier
  +    versions of Apache only supported Apache in a console window
  +    for Windows 95/98.</p>
  +
  +    <p>There is some support for Apache on Windows 95/98 to behave
  +    in a similar manner as a service on Windows NT/2000. It is
  +    <em>highly experimental</em>, if it works (at all) the Apache
  +    Sofware Foundation will not attest to it's reliability or
  +    future support. Proceed at your own risk!</p>
  +
  +    <p>Once you have confirmed that Apache runs correctly at the <a
  +    href="windows.html#cmdline">Command Prompt</a> you can install,
  +    control and uninstall it with the same commands as the Windows
  +    NT/2000 version.</p>
  +
  +    <p>There are, however, significant differences that you should
  +    note:</p>
  +
  +    <p>Apache will attempt to start and if successful it will run
  +    in the background. If you run the command</p>
  +<pre>
      Apache -n "service name" -k start
  -</PRE>
  +</pre>
  +
  +    <p>via a shortcut on your desktop, for example, then if the
  +    service starts successfully a console window will flash up but
  +    immediately disappears. If Apache detects any errors on startup
  +    such as a incorrect entries in the httpd.conf file, then the
  +    console window will remain visible. This will display an error
  +    message which will be useful in tracking down the cause of the
  +    problem.</p>
  +
  +    <p>Windows 95/98 does not support NET START or NET STOP
  +    commands so you must use Apache's Service Control options at a
  +    command prompt. You may wish to set up a shortcut for each of
  +    these commands so that you can just choose it from the start
  +    menu or desktop to perform the required action.</p>
  +
  +    <p>Apache and Windows 95/98 offer no support for running the
  +    Apache service as a specific user with network privilages. In
  +    fact, Windows 95/98 offers no security on the local machine,
  +    either. This is the simple reason that the Apache Software
  +    Foundation never endorses the use of Windows 95/98 as a public
  +    httpd server. These facilities exist only to assist the user in
  +    developing web content and learning the Apache server, and
  +    perhaps as a intranet server on a secured, private network.</p>
  +    <!--#include virtual="footer.html" -->
  +  </body>
  +</html>
   
  -   <p>via a shortcut on your desktop, for example, then if the service starts 
  -   successfully a console window will flash up but immediately disappears.
  -   If Apache detects any errors  on startup such as a incorrect entries in the
  -   httpd.conf file, then the console window will remain visible. This will 
  -   display an error message which will be useful in tracking down the cause of
  -   the problem.</P>
  -
  -<P>Windows 95/98 does not support NET START or NET STOP commands so you must 
  -   use Apache's Service Control options at a command prompt. You may wish to 
  -   set up a shortcut for each of these commands so that you can just choose 
  -   it from the start menu or desktop to perform the required action.</P>
  -
  -<P>Apache and Windows 95/98 offer no support for running the Apache service 
  -   as a specific user with network privilages.  In fact, Windows 95/98 offers
  -   no security on the local machine, either.  This is the simple reason that
  -   the Apache Software Foundation never endorses the use of Windows 95/98 as a
  -   public httpd server.  These facilities exist only to assist the user in
  -   developing web content and learning the Apache server, and perhaps as a
  -   intranet server on a secured, private network.</P>
  -
  -<!--#include virtual="footer.html" -->
  -</BODY>
  -</HTML>
  
  
  
  1.43      +506 -444  httpd-2.0/docs/manual/platform/windows.html
  
  Index: windows.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/platform/windows.html,v
  retrieving revision 1.42
  retrieving revision 1.43
  diff -u -r1.42 -r1.43
  --- windows.html	2001/08/22 22:34:50	1.42
  +++ windows.html	2001/09/22 19:37:51	1.43
  @@ -1,517 +1,579 @@
  -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
  -<HTML>
  -<HEAD>
  -<TITLE>Using Apache with Microsoft Windows</TITLE>
  -</HEAD>
  -
  -<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  -<BODY
  - BGCOLOR="#FFFFFF"
  - TEXT="#000000"
  - LINK="#0000FF"
  - VLINK="#000080"
  - ALINK="#FF0000"
  ->
  -<!--#include virtual="header.html" -->
  -
  -<H1 ALIGN="CENTER">Using Apache with Microsoft Windows</H1>
  -
  -<P>This document explains how to install, configure and run
  -   Apache 2.0 under Microsoft Windows. If you find any bugs, or wish 
  -   to contribute in other ways, please use our 
  -   <A HREF="http://www.apache.org/bugs/">bug reporting page.</A></P>
  -
  -<P>Most of this document assumes that you are installing Windows from a
  -   binary distribution. If you want to compile Apache yourself (possibly
  -   to help with development, or to track down bugs), see 
  -   <A HREF="win_compiling.html">Compiling Apache for Microsoft Windows</A>.
  -
  -<P><STRONG>At this time, support for Windows 95, 98 and ME is incomplete.
  -   Apache 2.0 is not expected to work on those platforms at this time.</STRONG>
  -   If you are interested in helping with that effort, please see the 
  -   developer's site for information on <a href="http://dev.apache.org/">how 
  -   to get involved</a>.  Support will likely be provided at some point in the
  -   future, and patches to allow Apache to work on 95, 98 and ME are welcome!</P>
  -
  -<HR>
  -
  -<UL>
  -  <LI><A HREF="#req">Requirements</A>
  -  <LI><A HREF="#down">Downloading Apache for Windows</A>
  -  <LI><A HREF="#inst">Installing Apache for Windows (binary install)</A>
  -  <LI><A HREF="#run">Running Apache for Windows</A>
  -  <LI><A HREF="#use">Using Apache for Windows</A>
  -  <LI><A HREF="#cmdline">Running Apache for Windows from the Command Line</A>
  -  <LI><A HREF="win_service.html">Running Apache for Windows as a Service</A>
  -  <LI><A HREF="win_service.html#signal">Controlling Apache as a Service</A>
  -  <LI><A HREF="win_compiling.html">Compiling Apache for Microsoft Windows</A>
  -</UL>
  -
  -<HR>
  -
  -<H2><A NAME="req">Requirements</A></H2>
  -
  -<P>Apache 2.0 is designed to run on Windows NT 4.0 and Windows 2000. The 
  -   binary installer will only work with the x86 family of processors, such
  -   as Intel's. Apache may also run on Windows 95, 98 and ME, but these are
  -   not tested, and are never recommended for production servers. In all 
  -   cases TCP/IP networking must be installed.</P>
  -
  -<P>If running on Windows 95, the "Winsock2" upgrade MUST BE INSTALLED. 
  -   "Winsock2" for Windows 95 is available 
  -   <A HREF="http://www.microsoft.com/windows95/downloads/">here</A>.</P>
  -
  -<P>If running on NT 4.0, installing Service Pack 3 or 6 is recommended, as
  -   Service Pack 4 created known issues with TCP/IP and WinSock integrity that
  -   were resolved in later Service Packs.</P>
  -
  -<H2><A NAME="down">Downloading Apache for Windows</A></H2>
  -
  -<P>Information on the latest version of Apache can be found on the
  -   Apache web server at <A HREF="http://httpd.apache.org/">
  -   http://httpd.apache.org/</A>.  This will list the current release, 
  -   any more recent alpha or beta-test releases, together with details of 
  -   mirror web and anonymous ftp sites.</P>
  -
  -<P>You should download the version of Apache for Windows with the
  -   <CODE>.msi</CODE> extension. This is a single Microsoft Installer file
  -   containing Apache, ready to install and run. There is a seperate 
  -   <CODE>.zip</CODE> file containing _only_ the source code, to compile 
  -   Apache yourself with the Microsoft Visual C++ (Visual Studio) tools.</P>
  -
  -<H2><A NAME="inst">Installing Apache for Windows</A></H2>
  -
  -<P>Run the Apache <SAMP>.msi</SAMP> file you downloaded above. This will
  -   ask for:</P>
  -
  -<UL>
  -
  - <LI>the directory to install Apache into (the default is 
  -    <CODE>\Program Files\Apache Group\Apache</CODE> although you can
  -    change this to any other directory)
  -
  - <LI>the start menu name (default is "Apache Web Server")
  -
  - <LI>the installation type. The "Typical" option installs
  -    everything except the source code. The "Minimum" option does not
  -    install the manuals or source code. Choose the "Custom" install if
  -    you want to install the source code.
  -
  -</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.</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 a 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.</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">"service"</A> (available on 
  -    Windows NT/2000, or a pseudo-service on Windows 95, 98 or ME).
  -    This is the best option if you want Apache to automatically start when you 
  -    machine boots, and to keep Apache running when you log-off.
  - <LI>From a <A HREF="#cmdline">console window</A>. This MUST be used by any
  -    administrator to test before to attempting to run as a service.
  -</UL>
  -
  -<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
  -   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>
  -   
  -<P>If the Apache console window closes immediately (or unexpectedly),
  -   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 change to the logs folder, and review
  -   the error.log file for configuration mistakes.  If you accepted the
  -   defaults when you installed Apache, the commands would be:</P>
  +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  +    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   
  -<PRE>
  +<html xmlns="http://www.w3.org/1999/xhtml">
  +  <head>
  +    <meta name="generator" content="HTML Tidy, see www.w3.org" />
  +
  +    <title>Using Apache with Microsoft Windows</title>
  +  </head>
  +  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  +
  +  <body bgcolor="#FFFFFF" text="#000000" link="#0000FF"
  +  vlink="#000080" alink="#FF0000">
  +    <!--#include virtual="header.html" -->
  +
  +    <h1 align="CENTER">Using Apache with Microsoft Windows</h1>
  +
  +    <p>This document explains how to install, configure and run
  +    Apache 2.0 under Microsoft Windows. If you find any bugs, or
  +    wish to contribute in other ways, please use our <a
  +    href="http://www.apache.org/bugs/">bug reporting page.</a></p>
  +
  +    <p>Most of this document assumes that you are installing
  +    Windows from a binary distribution. If you want to compile
  +    Apache yourself (possibly to help with development, or to track
  +    down bugs), see <a href="win_compiling.html">Compiling Apache
  +    for Microsoft Windows</a>.</p>
  +
  +    <p><strong>At this time, support for Windows 95, 98 and ME is
  +    incomplete. Apache 2.0 is not expected to work on those
  +    platforms at this time.</strong> If you are interested in
  +    helping with that effort, please see the developer's site for
  +    information on <a href="http://dev.apache.org/">how to get
  +    involved</a>. Support will likely be provided at some point in
  +    the future, and patches to allow Apache to work on 95, 98 and
  +    ME are welcome!</p>
  +    <hr />
  +
  +    <ul>
  +      <li><a href="#req">Requirements</a></li>
  +
  +      <li><a href="#down">Downloading Apache for Windows</a></li>
  +
  +      <li><a href="#inst">Installing Apache for Windows (binary
  +      install)</a></li>
  +
  +      <li><a href="#run">Running Apache for Windows</a></li>
  +
  +      <li><a href="#use">Using Apache for Windows</a></li>
  +
  +      <li><a href="#cmdline">Running Apache for Windows from the
  +      Command Line</a></li>
  +
  +      <li><a href="win_service.html">Running Apache for Windows as
  +      a Service</a></li>
  +
  +      <li><a href="win_service.html#signal">Controlling Apache as a
  +      Service</a></li>
  +
  +      <li><a href="win_compiling.html">Compiling Apache for
  +      Microsoft Windows</a></li>
  +    </ul>
  +    <hr />
  +
  +    <h2><a id="req" name="req">Requirements</a></h2>
  +
  +    <p>Apache 2.0 is designed to run on Windows NT 4.0 and Windows
  +    2000. The binary installer will only work with the x86 family
  +    of processors, such as Intel's. Apache may also run on Windows
  +    95, 98 and ME, but these are not tested, and are never
  +    recommended for production servers. In all cases TCP/IP
  +    networking must be installed.</p>
  +
  +    <p>If running on Windows 95, the "Winsock2" upgrade MUST BE
  +    INSTALLED. "Winsock2" for Windows 95 is available <a
  +    href="http://www.microsoft.com/windows95/downloads/">here</a>.</p>
  +
  +    <p>If running on NT 4.0, installing Service Pack 3 or 6 is
  +    recommended, as Service Pack 4 created known issues with TCP/IP
  +    and WinSock integrity that were resolved in later Service
  +    Packs.</p>
  +
  +    <h2><a id="down" name="down">Downloading Apache for
  +    Windows</a></h2>
  +
  +    <p>Information on the latest version of Apache can be found on
  +    the Apache web server at <a
  +    href="http://httpd.apache.org/">http://httpd.apache.org/</a>.
  +    This will list the current release, any more recent alpha or
  +    beta-test releases, together with details of mirror web and
  +    anonymous ftp sites.</p>
  +
  +    <p>You should download the version of Apache for Windows with
  +    the <code>.msi</code> extension. This is a single Microsoft
  +    Installer file containing Apache, ready to install and run.
  +    There is a seperate <code>.zip</code> file containing _only_
  +    the source code, to compile Apache yourself with the Microsoft
  +    Visual C++ (Visual Studio) tools.</p>
  +
  +    <h2><a id="inst" name="inst">Installing Apache for
  +    Windows</a></h2>
  +
  +    <p>Run the Apache <samp>.msi</samp> file you downloaded above.
  +    This will ask for:</p>
  +
  +    <ul>
  +      <li>the directory to install Apache into (the default is
  +      <code>\Program Files\Apache Group\Apache</code> although you
  +      can change this to any other directory)</li>
  +
  +      <li>the start menu name (default is "Apache Web Server")</li>
  +
  +      <li>the installation type. The "Typical" option installs
  +      everything except the source code. The "Minimum" option does
  +      not install the manuals or source code. Choose the "Custom"
  +      install if you want to install the source code.</li>
  +    </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.</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 a 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.</p>
  +
  +    <h2><a id="run" 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">"service"</a>
  +      (available on Windows NT/2000, or a pseudo-service on Windows
  +      95, 98 or ME). This is the best option if you want Apache to
  +      automatically start when you machine boots, and to keep
  +      Apache running when you log-off.</li>
  +
  +      <li>From a <a href="#cmdline">console window</a>. This MUST
  +      be used by any administrator to test before to attempting to
  +      run as a service.</li>
  +    </ul>
  +
  +    <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 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>
  +
  +    <p>If the Apache console window closes immediately (or
  +    unexpectedly), 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 change to the logs folder, and 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>
  +  <samp>Wait for Apache to exit, or press Ctrl+C</samp>
     cd logs
     more &lt;error.log
  -</PRE>
  +</pre>
   
  -<P><STRONG>Complete the steps above before you proceed to attempt to 
  -   start Apache as a Window NT/2000 service!</STRONG></P>
  -
  -<P>To start Apache as a service, you first need to install it as a
  -   service. Multiple Apache services can be installed, each with a
  -   different name and configuration.  To install the default Apache
  -   service named "Apache", run the "Install Apache as Service (NT only)"
  -   option from the Start menu. Once this is done you can start the "Apache"
  -   service by opening the Services window (in the Control Panel), selecting Apache,
  -   then clicking on Start. Apache will now be running in the background. You
  -   can later stop Apache by clicking on Stop. As an alternative to using
  -   the Services window, you can start and stop the "Apache" service from the control
  -   line with:</P>
  -
  -<PRE>
  +    <p><strong>Complete the steps above before you proceed to
  +    attempt to start Apache as a Window NT/2000
  +    service!</strong></p>
  +
  +    <p>To start Apache as a service, you first need to install it
  +    as a service. Multiple Apache services can be installed, each
  +    with a different name and configuration. To install the default
  +    Apache service named "Apache", run the "Install Apache as
  +    Service (NT only)" option from the Start menu. Once this is
  +    done you can start the "Apache" service by opening the Services
  +    window (in the Control Panel), selecting Apache, then clicking
  +    on Start. Apache will now be running in the background. You can
  +    later stop Apache by clicking on Stop. As an alternative to
  +    using the Services window, you can start and stop the "Apache"
  +    service from the control line with:</p>
  +<pre>
     NET START APACHE
     NET STOP APACHE
  -</PRE>
  -
  -<P>See <A HREF="#signalsrv">Signalling Service Apache when Running</A>
  -   for more information on installing and controlling Apache services.</P>
  +</pre>
   
  -<P><STRONG>Apache, unlike many other Windows NT/2000 services, logs any
  -   errors to it's own error.log file in the logs folder within the
  -   Apache server root folder.  You will <EM>not</EM> find Apache error 
  -   details in the Windows NT Event Log.</STRONG></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>
  -
  -<PRE>
  +    <p>See <a href="#signalsrv">Signalling Service Apache when
  +    Running</a> for more information on installing and controlling
  +    Apache services.</p>
  +
  +    <p><strong>Apache, unlike many other Windows NT/2000 services,
  +    logs any errors to it's own error.log file in the logs folder
  +    within the Apache server root folder. You will <em>not</em>
  +    find Apache error details in the Windows NT Event
  +    Log.</strong></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>
  +<pre>
     http://localhost/
  -</PRE>
  -
  -<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>
   
  -<PRE>
  +    <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>
  +</pre>
   
  -<P>Once your basic installation is working, you should configure it
  -   properly by editing the files in the <SAMP>conf</SAMP> directory.
  -   Again, if you change the configuration of the Windows NT/2000
  -   service for Apache, first attempt to start it from the command
  -   line to assure that the service starts with no errors.</P>
  -
  -<P>Because Apache <em>CANNOT</em> share the same port with another
  -   TCPIP 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.</P>
  -
  -<H2><A NAME="use">Configuring Apache for Windows</A></H2>
  -
  -<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>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/mpm_common.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.
  -	   <STRONG>
  -           Warning: The server configuration file is reread when the
  -           new child process is started. If you have modified httpd.conf,
  -           the new child may not start or you may receive unexpected results.
  -	   </STRONG>
  -      <P><A HREF="../mod/mpm_common.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
  -         can handle at once; be sure and set this number high enough for
  -         your site if you get a lot of hits. The recommended default is
  -         <CODE>ThreadsPerChild 50</CODE>.</P>
  -  <LI><P>The directives that accept filenames as arguments now must use
  -      Windows filenames instead of Unix ones. However, because Apache
  -      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,
  -      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
  -      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
  -      in <CODE>access.conf</CODE>):</P>
  -<PRE>
  +    <p>Once your basic installation is working, you should
  +    configure it properly by editing the files in the
  +    <samp>conf</samp> directory. Again, if you change the
  +    configuration of the Windows NT/2000 service for Apache, first
  +    attempt to start it from the command line to assure that the
  +    service starts with no errors.</p>
  +
  +    <p>Because Apache <em>CANNOT</em> share the same port with
  +    another TCPIP 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.</p>
  +
  +    <h2><a id="use" name="use">Configuring Apache for
  +    Windows</a></h2>
  +
  +    <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>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>
  +
  +        <p>So the "process"-management directives are
  +        different:</p>
  +
  +        <p><a
  +        href="../mod/mpm_common.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.
  +        <strong>Warning: The server configuration file is reread
  +        when the new child process is started. If you have modified
  +        httpd.conf, the new child may not start or you may receive
  +        unexpected results.</strong></p>
  +
  +        <p><a
  +        href="../mod/mpm_common.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 can handle at once; be sure and set
  +        this number high enough for your site if you get a lot of
  +        hits. The recommended default is <code>ThreadsPerChild
  +        50</code>.</p>
  +      </li>
  +
  +      <li>
  +        <p>The directives that accept filenames as arguments now
  +        must use Windows filenames instead of Unix ones. However,
  +        because Apache 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>
  +
  +      <li>
  +        <p>Apache for Windows contains 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 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 in
  +        <code>access.conf</code>):</p>
  +<pre>
       LoadModule status_module modules/mod_status.so
  -</PRE>
  -      <P>Information on <A HREF="../mod/mod_so.html#creating">creating loadable
  -         modules</A> is also available.</P>
  -  <LI><P>Apache can also load ISAPI Extensions (<EM>i.e.</EM>, Internet Server
  -         Applications), such as those used by Microsoft's IIS, and other
  -         Windows servers. <A HREF="../mod/mod_isapi.html">More information
  -         is available.</A>  Note that Apache <em>CANNOT</em> load ISAPI
  -		 Filters.
  -  <LI>When running CGI scripts, the method Apache uses to find the
  -        interpreter for the script is configurable using the
  -        <a href="../mod/core.html#scriptinterpretersource"
  -        >ScriptInterpreterSource</a> directive.
  -   <LI>Since it is often difficult to manage files with names like
  -        <code>.htaccess</code> under windows, you may find it useful
  -        to change the name of this configuration file using the
  -        <a href="../mod/core.html#accessfilename">AccessFilename</a>
  -        directive.
  -
  -
  -</UL>
  -
  -<H2><A NAME="service">Running Apache for Windows as a Service</A></H2>
  -
  -<P><STRONG>Note: The -n option to specify a service name is only available
  -   with Apache 1.3.7 and later.  Earlier versions of Apache only support
  -   the default service name 'Apache'.</STRONG></P>
  -
  -<P>You can install Apache as a Windows NT service as follows:</p>
  +</pre>
   
  -<PRE>
  +        <p>Information on <a
  +        href="../mod/mod_so.html#creating">creating loadable
  +        modules</a> is also available.</p>
  +      </li>
  +
  +      <li>
  +        <p>Apache can also load ISAPI Extensions (<em>i.e.</em>,
  +        Internet Server Applications), such as those used by
  +        Microsoft's IIS, and other Windows servers. <a
  +        href="../mod/mod_isapi.html">More information is
  +        available.</a> Note that Apache <em>CANNOT</em> load ISAPI
  +        Filters.</p>
  +      </li>
  +
  +      <li>When running CGI scripts, the method Apache uses to find
  +      the interpreter for the script is configurable using the <a
  +      href="../mod/core.html#scriptinterpretersource">ScriptInterpreterSource</a>
  +      directive.</li>
  +
  +      <li>Since it is often difficult to manage files with names
  +      like <code>.htaccess</code> under windows, you may find it
  +      useful to change the name of this configuration file using
  +      the <a
  +      href="../mod/core.html#accessfilename">AccessFilename</a>
  +      directive.</li>
  +    </ul>
  +
  +    <h2><a id="service" name="service">Running Apache for Windows
  +    as a Service</a></h2>
  +
  +    <p><strong>Note: The -n option to specify a service name is
  +    only available with Apache 1.3.7 and later. Earlier versions of
  +    Apache only support the default service name
  +    'Apache'.</strong></p>
  +
  +    <p>You can install Apache as a Windows NT service as
  +    follows:</p>
  +<pre>
       apache -k install -n "service name"
  -</PRE>
  +</pre>
   
  -  <p>To install a service to use a particular configuration, specify the
  -  configuration file when the service is installed:</p>
  -
  -<PRE>
  +    <p>To install a service to use a particular configuration,
  +    specify the configuration file when the service is
  +    installed:</p>
  +<pre>
       apache -k install -n "service name" -f "\my server\conf\my.conf"
  -</PRE>
  -
  -  <p>To remove an Apache service, use</p>
  +</pre>
   
  -<PRE>
  +    <p>To remove an Apache service, use</p>
  +<pre>
       apache -k uninstall -n "service name"
  -</PRE>
  -
  -  <p>The default "service name", if one is not specified, is "Apache".</P>
  +</pre>
   
  -<P>Once a service is installed, you can use the <SAMP>-n</SAMP> option, in 
  -   conjunction with other options, to refer to a service's configuration 
  -   file.  For example:</P>
  +    <p>The default "service name", if one is not specified, is
  +    "Apache".</p>
   
  -<P>To test a service's configuration file:</P>
  +    <p>Once a service is installed, you can use the <samp>-n</samp>
  +    option, in conjunction with other options, to refer to a
  +    service's configuration file. For example:</p>
   
  -<PRE>
  +    <p>To test a service's configuration file:</p>
  +<pre>
       apache -n "service name" -t
  -</PRE>
  +</pre>
   
  -<P>To start a console Apache using a service's configuration file:</P>
  -
  -<PRE>
  +    <p>To start a console Apache using a service's configuration
  +    file:</p>
  +<pre>
       apache -n "service name"
  -</PRE>
  -
  -<P><STRONG>Important Note on service dependencies:</STRONG></P>
  +</pre>
   
  -<P>Prior to Apache release 1.3.13, the dependencies required to
  -   successfully start an installed service were not configured.
  -   After installing a service using earlier versions of Apache, 
  -   you must follow these steps:
  +    <p><strong>Important Note on service dependencies:</strong></p>
   
  -<PRE>
  +    <p>Prior to Apache release 1.3.13, the dependencies required to
  +    successfully start an installed service were not configured.
  +    After installing a service using earlier versions of Apache,
  +    you must follow these steps:</p>
  +<pre>
       Run regedt32
  -    Select <U>W</U>indow - "HKEY_LOCAL_MACHINE on Local Machine" from the menu
  +    Select <u>W</u>indow - "HKEY_LOCAL_MACHINE on Local Machine" from the menu
       Double-click to open the SYSTEM, then the CurrentControlSet keys
       Scroll down and click on the Apache servicename
  -    Select <U>E</U>dit - Add <U>V</U>alue... from the menu
  +    Select <u>E</u>dit - Add <u>V</u>alue... from the menu
       Fill in the Add Value dialog with 
  -        <U>V</U>alue Name: DependOnGroup 
  -        <U>D</U>ata Type: REG_MULTI_SZ
  +        <u>V</u>alue Name: DependOnGroup 
  +        <u>D</u>ata Type: REG_MULTI_SZ
           and click OK
       Leave the Multi-String Editor dialog empty and click OK
  -    Select <U>E</U>dit - Add <U>V</U>alue... from the menu
  +    Select <u>E</u>dit - Add <u>V</u>alue... from the menu
       Fill in the Add Value dialog with 
  -        <U>V</U>alue Name: DependOnService
  -        <U>D</U>ata Type: REG_MULTI_SZ
  +        <u>V</u>alue Name: DependOnService
  +        <u>D</u>ata Type: REG_MULTI_SZ
           and click OK
       Type the following list (one per line) in the Multi-String Editor dialog
           Tcpip
           Afd
           and click OK
  -</PRE>
  -
  -<P>If you are using COM or DCOM components from a third party module, ISAPI,
  -   or other add-in scripting technologies such as ActiveState Perl, you may
  -   also need to add the entry Rpcss to the DependOnService list.  To avoid
  -   exposing the TCP port 135 when it is unnecessary, Apache does not create
  -   that entry upon installation.  Follow the directions above to find or 
  -   create the DependOnService value, double click that value if it already 
  -   exists, and add the Rpcss entry to the list.</P>
  +</pre>
   
  -<H2><A NAME="cmdline">Running Apache for Windows from the Command Line</A></H2>
  -
  -<P>The Start menu icons and the NT Service manager can provide a simple
  -   interface for administering Apache. But in some cases it is easier to
  -   work from the command line.</P>
  -
  -<P>When working with Apache it is important to know how it will find the
  -   configuration files.  You can specify a configuration file on the command line
  -   in two ways:</p>
  -
  -<UL>
  -	<LI>-f specifies a path to a particular configuration file
  -</UL>
  +    <p>If you are using COM or DCOM components from a third party
  +    module, ISAPI, or other add-in scripting technologies such as
  +    ActiveState Perl, you may also need to add the entry Rpcss to
  +    the DependOnService list. To avoid exposing the TCP port 135
  +    when it is unnecessary, Apache does not create that entry upon
  +    installation. Follow the directions above to find or create the
  +    DependOnService value, double click that value if it already
  +    exists, and add the Rpcss entry to the list.</p>
  +
  +    <h2><a id="cmdline" name="cmdline">Running Apache for Windows
  +    from the Command Line</a></h2>
  +
  +    <p>The Start menu icons and the NT Service manager can provide
  +    a simple interface for administering Apache. But in some cases
  +    it is easier to work from the command line.</p>
  +
  +    <p>When working with Apache it is important to know how it will
  +    find the configuration files. You can specify a configuration
  +    file on the command line in two ways:</p>
  +
  +    <ul>
  +      <li>-f specifies a path to a particular configuration
  +      file</li>
  +    </ul>
  +<pre>
  +    apache -f "c:\my server\conf\my.conf"
  +    apache -f test\test.conf
  +</pre>
  +
  +    <ul>
  +      <li>-n specifies the configuration file of an installed
  +      Apache service (Apache 1.3.7 and later)</li>
  +    </ul>
  +<pre>
  +    apache -n "service name"
  +</pre>
   
  -<PRE>    apache -f "c:\my server\conf\my.conf"
  -    apache -f test\test.conf</PRE>
  +    <p>In these cases, the proper ServerRoot should be set in the
  +    configuration file.</p>
   
  -<UL>
  -	<LI>-n specifies the configuration file of an installed Apache service (Apache 1.3.7 and later)
  -</UL>
  +    <p>If you don't specify a configuration file name with -f or
  +    -n, Apache will use the file name compiled into the server,
  +    usually "conf/httpd.conf". Invoking Apache with the -V switch
  +    will display this value labeled as SERVER_CONFIG_FILE. Apache
  +    will then determine its ServerRoot by trying the following, in
  +    this order:</p>
   
  -<PRE>    apache -n "service name"</PRE>
  +    <ul>
  +      <li>A ServerRoot directive via a -C switch.</li>
   
  -   <p>In these cases, the proper ServerRoot should be set in the configuration file.</P>
  +      <li>The -d switch on the command line.</li>
   
  -<P>If you don't specify a configuration file name with -f or -n, Apache will
  -   use the file name compiled into the server, usually "conf/httpd.conf".  Invoking
  -   Apache with the -V switch will display this value labeled as SERVER_CONFIG_FILE.
  -   Apache will then determine its ServerRoot by trying the following, in this order:</P>
  +      <li>Current working directory</li>
   
  -<UL>
  -	<LI>A ServerRoot directive via a -C switch.
  -	<LI>The -d switch on the command line.
  -	<LI>Current working directory
  -	<LI>A registry entry, created if you did a binary install.
  -	<LI>The server root compiled into the server.
  -</UL>
  +      <li>A registry entry, created if you did a binary
  +      install.</li>
   
  -<P>The server root compiled into the server is usually "/apache".
  -   invoking apache with the -V switch will display this value
  -   labeled as HTTPD_ROOT.</P>
  +      <li>The server root compiled into the server.</li>
  +    </ul>
   
  -<P>When invoked from the start menu, Apache is usually passed no arguments,
  -   so using the registry entry is the preferred technique for console Apache.</P>
  +    <p>The server root compiled into the server is usually
  +    "/apache". invoking apache with the -V switch will display this
  +    value labeled as HTTPD_ROOT.</p>
   
  -<P>During a binary installation, a version-specific registry key is created 
  -   in the Windows registry:
  +    <p>When invoked from the start menu, Apache is usually passed
  +    no arguments, so using the registry entry is the preferred
  +    technique for console Apache.</p>
   
  -<PRE>
  +    <p>During a binary installation, a version-specific registry
  +    key is created in the Windows registry:</p>
  +<pre>
     HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\1.3.7
   
     HKEY_LOCAL_MACHINE\Software\Apache Group\Apache\2.0a3
  -</PRE>
  -
  -<P>This key is compiled into the server and can enable you to test 
  -   new versions without affecting the current version.  Of course
  -   you must take care not to install the new version on top of the
  -   old version in the file system.</P>
  -
  -<P>If you did not do a binary install then Apache will in some
  -   scenarios complain that about the missing registry key.  This
  -   warning can be ignored if it otherwise was able to find its
  -   configuration files.</P>
  -
  -<P>The value of this key is the "ServerRoot" directory, containing the
  -   <SAMP>conf</SAMP> directory. When Apache starts it will read the
  -   <SAMP>httpd.conf</SAMP> file from this directory. If this file
  -   contains a <SAMP>ServerRoot</SAMP> directive which is different from
  -   the directory obtained from the registry key above, Apache will forget
  -   the registry key and use the directory from the configuration file.
  -   If you copy the Apache directory or configuration files to a new
  -   location it is vital that you update the <SAMP>ServerRoot</SAMP>
  -   directory in the <SAMP>httpd.conf</SAMP> file to the new location.
  -
  -<P>To run Apache from the command line as a console application, use the
  -   following command:</p>
  +</pre>
   
  -<PRE>
  +    <p>This key is compiled into the server and can enable you to
  +    test new versions without affecting the current version. Of
  +    course you must take care not to install the new version on top
  +    of the old version in the file system.</p>
  +
  +    <p>If you did not do a binary install then Apache will in some
  +    scenarios complain that about the missing registry key. This
  +    warning can be ignored if it otherwise was able to find its
  +    configuration files.</p>
  +
  +    <p>The value of this key is the "ServerRoot" directory,
  +    containing the <samp>conf</samp> directory. When Apache starts
  +    it will read the <samp>httpd.conf</samp> file from this
  +    directory. If this file contains a <samp>ServerRoot</samp>
  +    directive which is different from the directory obtained from
  +    the registry key above, Apache will forget the registry key and
  +    use the directory from the configuration file. If you copy the
  +    Apache directory or configuration files to a new location it is
  +    vital that you update the <samp>ServerRoot</samp> directory in
  +    the <samp>httpd.conf</samp> file to the new location.</p>
  +
  +    <p>To run Apache from the command line as a console
  +    application, use the following command:</p>
  +<pre>
       apache 
  -</PRE>
  +</pre>
   
  -   <p>Apache will execute, and will remain running until it is stopped by pressing
  -   control-C.</P>
  +    <p>Apache will execute, and will remain running until it is
  +    stopped by pressing control-C.</p>
   
  -<H2><A NAME="signalsrv">Signalling Service Apache when running</A></H2>
  +    <h2><a id="signalsrv" name="signalsrv">Signalling Service
  +    Apache when running</a></h2>
   
  -<P>On Windows NT, multiple instances of Apache can be run as services.
  -   Signal an Apache service to start, restart, or shutdown as follows:</P>
  -
  -<PRE>
  +    <p>On Windows NT, multiple instances of Apache can be run as
  +    services. Signal an Apache service to start, restart, or
  +    shutdown as follows:</p>
  +<pre>
       apache -n "service name" -k start
       apache -n "service name" -k restart
       apache -n "service name" -k shutdown
  -</PRE>
  -
  -<P>In addition, you can use the native NT NET command to
  -   start and stop Apache services as follows:</P>
  +</pre>
   
  -<PRE>
  +    <p>In addition, you can use the native NT NET command to start
  +    and stop Apache services as follows:</p>
  +<pre>
       NET START "service name"
       NET STOP "service name"
  -</PRE>
  -
  -<H2><A NAME="signal">Signalling Console Apache when running</A></H2>
  +</pre>
   
  -<P>On Windows 95, Apache runs as a console application. You can tell a
  -   running Apache to stop by opening another console window and typing:</P>
  +    <h2><a id="signal" name="signal">Signalling Console Apache when
  +    running</a></h2>
   
  -<PRE>
  +    <p>On Windows 95, Apache runs as a console application. You can
  +    tell a running Apache to stop by opening another console window
  +    and typing:</p>
  +<pre>
       apache -k shutdown
  -</PRE>
  -
  -<P>This should be used instead of pressing Control-C in the running
  -   Apache console window, because it lets Apache end any current
  -   transactions and cleanup gracefully.</P>
  -
  -<P>You can also tell Apache to restart. This makes it re-read the
  -   configuration files. Any transactions in progress are allowed to
  -   complete without interruption. To restart Apache, run</P>
  +</pre>
   
  -<PRE>
  +    <p>This should be used instead of pressing Control-C in the
  +    running Apache console window, because it lets Apache end any
  +    current transactions and cleanup gracefully.</p>
  +
  +    <p>You can also tell Apache to restart. This makes it re-read
  +    the configuration files. Any transactions in progress are
  +    allowed to complete without interruption. To restart Apache,
  +    run</p>
  +<pre>
       apache -k restart
  -</PRE>
  +</pre>
   
  -<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>
  -</HTML>
  +    <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>
  +</html>