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
-NetWare. See the <A HREF="./">Apache documentation</A> for all the
+NetWare. See the <A HREF="../">Apache documentation</A> for all the
available directives.
<P>
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>
+ 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/status
</PRE>
- <P>Information on <A HREF="mod/mod_so.html#creating">creating loadable
+ <P>Information on <A HREF="../mod/mod_so.html#creating">creating loadable
modules</A> is also available.</P>
</UL>
<P>All major pieces of Apache may be built using the ApacheNW.mcp project
file. This includes modules such as status, info, and proxy. In addition,
- the following project files have been provided as well:
+ the following project files have been provided as well:</p>
+
<PRE>
/apache-1.3/src/support/htpasswd.mcp.gz
/apache-1.3/src/support/htdigest.mcp.gz
</PRE>
-</P>
-<CODE>htpasswd.mcp.gz</CODE> and <CODE>htdigest.mcp.gz</CODE> will also need
-to be unzipped before they can be used with MetroWerks CodeWarrior.
+<p><CODE>htpasswd.mcp.gz</CODE> and <CODE>htdigest.mcp.gz</CODE> will also need
+to be unzipped before they can be used with MetroWerks CodeWarrior.</p>
<P>Once Apache has been compiled, it needs to be installed in its server
root directory. The default is the <CODE>sys:/Apache</CODE>
Copy the *.conf-dist-nw from the distribution conf directory
and rename *.conf. Edit the ServerRoot entries to your
actual server root (for example "sys:/apache"). Copy over
-the conf/magic and conf/mime.types files as well.
+the conf/magic and conf/mime.types files as well.</p>
<!--#include virtual="footer.html" -->
</BODY>
>Where are the performance bottlenecks for Alpha AXP running the
>Netscape Commerce Server 1.12 with high volume internet traffic?
>We are evaluating network performance for a variety of Alpha AXP
->runing DEC UNIX 3.2C, which run DEC's seal firewall and behind
+>running DEC UNIX 3.2C, which run DEC's seal firewall and behind
>that Alpha 1000 and 2100 webservers.
Our experience (running such Web servers as <A
version of V4.0.
-Jeff
+</pre>
<HR>
-----------------------------------------------------------------------------
+<pre>----------------------------------------------------------------------------
From mogul@pa.dec.com (Jeffrey Mogul)
Organization DEC Western Research
ipport_userreserved The maximum number of concurrent non-reserved,
dynamically allocated ports. Default range
is 1025-5000. The maximum value is 65535.
- This limits the numer of times you can
+ This limits the number of times you can
simultaneously telnet or ftp out to connect
to other systems.
ipport_userreserved - X -
sysconfig -q inet - - X
sysconfig -q socket - - X
-
</PRE>
+
<!--#include virtual="footer.html" -->
</BODY>
</HTML>
(Transaction Processing Facility) operating system.
Unless otherwise noted TPF version 4.1 PUT09 is required.
<BR><BR>
- Refer to htdocs/manual/<A HREF="install-tpf.html">install-tpf.html</A>
+ Refer to htdocs/manual/<A HREF="../install-tpf.html">install-tpf.html</A>
for step-by-step installation instructions.
<BR><BR>
As this is the first cut at making Apache run on TPF,
performance tuning has not been done.
<BR><BR>
- This port builds upon the <A HREF="ebcdic.html">EBCDIC changes</A>
+ This port builds upon the <A HREF="../ebcdic.html">EBCDIC changes</A>
previously made to Apache.
<BR>
</P>
information in the resulting files, making it easier to find bugs and
track down problems.</P>
-<P>Apache can also be compiled using VC++'s Visual Studio development
- environment. To simplify this process, a Visual Studio workspace,
+<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
<LI><CODE>Apache.dsp <EM>requires ApacheCore and aprlibdll</EM></CODE>
</OL>
- In addition, the <CODE>os\win32</CODE> subdirectory contains
- project files for the optional modules.
+ <p>In addition, the <CODE>os\win32</CODE> subdirectory contains
+ project files for the optional modules.</p>
<OL>
<LI><CODE>os\win32\ApacheModuleAuthAnon.dsp</CODE>
<LI><CODE>modules\proxy\ApacheModuleProxy.dsp</CODE>
</OL>
- The <CODE>support\</CODE> folder contains project files for additional
+ <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>
directory, on the current hard drive. </P>
<P>To build and install all the files into the desired folder <EM>dir</EM>
- automatically, use one the following nmake commands:
+ automatically, use one the following nmake commands:</p>
<UL>
<LI><CODE>nmake /f Makefile.win installr INSTDIR=<EM>dir</EM></CODE>
(for debug build)
</UL>
- The <EM>dir</EM> argument to INSTDIR gives the installation directory; it
+ <p>The <EM>dir</EM> argument to INSTDIR gives the installation directory; it
can be omitted if Apache is to be installed into <SAMP>\Apache</SAMP>.</P>
<P>This will install the following:</P>
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 withing the Microsoft DeveloperStudio environment.</P>
+ you build from within the Microsoft DeveloperStudio environment.</P>
<P>Before running the server you must fill out the conf directory.
Copy the *.conf-dist-win from the distribution conf directory
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#test">procedure</a>
+ 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><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 ->
- Settings -> Control Panel -> Services -> apache service ... and click
+ that user, and use the the 'Log On As:' option. Select the Start Menu ->
+ Settings -> Control Panel -> Services -> apache service ... and click
the "Startup" button to access this setting.</P>
<BLOCKQUOTE>
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.</STRONG></P>
+ required network resource.</P>
<H2><A NAME="trouble">Troubleshooting Apache for Windows as a Service</A></H2>
</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#test">Testing Apache at the Command Prompt</a>.</P>
+ 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
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#test">Command Prompt</a> you can install, control
+ <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
+ background. If you run the command</p>
<PRE>
Apache -n "service name" -k start
</PRE>
- via a shortcut on your desktop, for example, then if the service starts
+ <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
>
<!--#include virtual="header.html" -->
-<H1 ALIGN="CENTER">Using Apache With Microsoft Windows</H1>
+<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
<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 TCPIP/WinSock integrety that
+ Service Pack 4 created known issues with TCPIP/WinSock integrity that
were resolved in later Service Packs.</P>
<P><STRONG>Warning: as of alpha 2.0a4 Windows 95 (and possibly 98) do not
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 <EMP>CANNOT</EMP> share the same port with another
+<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
<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
+ Windows. See the <A HREF="../">Apache documentation</A> for all the
available directives.</P>
<P>The main differences in Apache for Windows are:</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 <EMP>CANNOT</EMP> load ISAPI
+ is available.</A> Note that Apache <em>CANNOT</em> load ISAPI
Filters.
</UL>
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>You can install Apache as a Windows NT service as follows:</p>
<PRE>
apache -k install -n "service name"
</PRE>
- To install a service to use a particular configuration, specify the
- configuration file when the service is installed:
+ <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>
- To remove an Apache service, use
+ <p>To remove an Apache service, use</p>
<PRE>
apache -k uninstall -n "service name"
</PRE>
- 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
<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:
+ in two ways:</p>
<UL>
-<LI>-f specifies a path to a particular configuration file
+ <LI>-f specifies a path to a particular configuration file
</UL>
-<PRE> apache -f "c:\my server\conf\my.conf"</PRE>
-<PRE> apache -f test\test.conf</PRE>
+
+<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>-n specifies the configuration file of an installed Apache service (Apache 1.3.7 and later)
</UL>
+
<PRE> apache -n "service name"</PRE>
- In these cases, the proper ServerRoot should be set in the configuration file.</P>
+ <p>In these cases, the proper ServerRoot should be set in the configuration file.</P>
<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 will then determine its ServerRoot by trying the following, in this order:</P>
<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.
+ <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>
<P>The server root compiled into the server is usually "/apache".
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:
+ following command:</p>
<PRE>
apache
</PRE>
- Apache will execute, and will remain running until it is stopped by pressing
+ <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>
projects / apache / commitdiff