pepper 01/07/11 16:52:35
Modified: htdocs/manual cygwin.html
Log:
S'more cygwin cleanup.
Revision Changes Path
1.3 +58 -60 httpd-docs-1.3/htdocs/manual/cygwin.html
Index: cygwin.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/cygwin.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- cygwin.html 2001/07/11 21:50:32 1.2
+++ cygwin.html 2001/07/11 23:52:35 1.3
@@ -14,7 +14,7 @@
>
<!--#include virtual="header.html" -->
-<h1 align="CENTER"><a name="help">Using Apache With Cygwin</a></h1>
+<h1 align="CENTER"><a name="help">Using Apache with Cygwin</a></h1>
<p>This document explains how to install, configure and run Apache 1.3 under
the <a href="http://www.cygwin.com";>Cygwin</a> layer for Microsoft
@@ -66,7 +66,7 @@
<li><a href="#diff">Differences from Apache for Windows (native)</a>
<li><a href="#req">Requirements</a>
<li><a href="#down">Downloading Apache for Cygwin</a>
- <li><a href="#inst">Configuring and installing Apache for Cygwin</a>
+ <li><a href="#inst">Configuring and Installing Apache for Cygwin</a>
<li><a href="#run">Running Apache for Cygwin</a>
<li><a href="#serv">Running Apache for Cygwin as a Service</a>
</ul>
@@ -117,7 +117,7 @@
Apache for Cygwin can be built with most of the available Apache modules
with
no or minimal changes. Many popular modules have been compiled and
tested with Apache for Cygwin, including <code>mod_dav</code>,
- <code>mod_ssl</code>, <code>mod_php</code>, mod_perl</code>,
+ <code>mod_ssl</code>, <code>mod_php</code>, <code>mod_perl</code>,
<code>mod_gzip</code>, and <code>mod_jserv</code>.
<p>While there are developers who directly support the Windows native port of
Apache, very few module developers do. That is why it is can be
@@ -168,30 +168,29 @@
<h2><a name="down">Downloading Apache for Cygwin</a></h2>
-<p>The Cygwin platform is supported out-of-the-box for Apache 1.3.20 and
- on. This means there is no extra download required for the Cygwin
+<p>The Cygwin platform is supported out of the box by Apache 1.3.20 and
+ later. This means there is no extra download required for the Cygwin
platform. The latest version of Apache can be found on the
- Apache web server at <a href="http://www.apache.org/httpd";>
- http://www.apache.org/httpd</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>
+ Apache httpd web site at <a
+ href="http://httpd.apache.org/";>http://httpd.apache.org/</a>. The
+ site lists the current release, any more recent development
+ versions, and information on any mirror sites.</p>
-<h2><a name="inst">Configuring and installing Apache for Cygwin</a></h2>
+<h2><a name="inst">Configuring and Installing Apache for Cygwin</a></h2>
<p>Apache on Cygwin is configured and compiled the same way as on Unix
systems. Refer to the general <a href="configuring.html">configuration</a>
and <a href="install.html">installation</a> documents for details.
-<p>There are three ways in configuring and building Apache for Cygwin,
+<p>There are three ways to configure and build Apache for Cygwin,
depending on how additional Apache modules should be used:</p>
<ul>
<li><strong>Static linked version</strong>
<p>To build a static linked version of <code>httpd</code> including
- additional modules you will have to give the following statements to
- the shell:</p>
+ additional modules, use the following commands in the shell:</p>
<pre>
$ cd apache_1.3.x
$ ./configure
[--enable-module=<i>module</i>|--add-module=<i>/path/to/module</i>]
@@ -200,9 +199,9 @@
<p>This will produce the required extra libraries or object files for
<i>module</i> and link everything to <code>src/httpd.exe</code>.</p>
-<li><strong>Shared core DLL linked version (one for all version)</strong>
+<li><strong>Shared core, DLL linked version ('one-for-all' version)</strong>
<p>To build a DLL version of <code>httpd</code> including additional
- modules you have to give the following statements to the shell:</p>
+ modules, use the following commands:</p>
<pre>
$ cd apache_1.3.x
$ ./configure --enable-rule=SHARED_CORE \
@@ -213,22 +212,21 @@
<p>This will produce the required extra libraries or object files which hold
all
static linked code. Then <code>dllwrap</code> and <code>dlltool</code> will
- export all of those (including any added extra module code) to the shared
+ export all of those (including any additional module code) to the shared
<code>libhttpd.dll</code> and create the <code>libhttpd.a</code> import
library which is required for linking <code>httpd.exe</code>.</p>
<li><strong>Shared DLL modules linked version</strong>
<p>This method is currently <strong>ONLY</strong> supported using
a patched version of <code>ld.exe</code>. Please see the
- <a href="#req">requirements</a> section on where to get that version.
+ <a href="#req">requirements</a> section for where to get that version.
<p>To build a dynamic loadable DLL version of <code>httpd</code> which can
- load DLL modules on the fly while runtime you have to proceed as
follows:</p>
+ load DLL modules on the fly (at runtime), proceed as follows:</p>
<ul>
-<li><p>First build Apache's shared core giving the following statements
- to the shell:</p>
+<li><p>First build Apache's shared core as follows:</p>
<pre>
$ cd apache_1.3.x
$ ./configure --enable-rule=SHARED_CORE --enable-module=so \
@@ -240,10 +238,10 @@
<p>Now the <code>make</code> process will break when trying to compile the
shared module defined using <code>--enable-shared</code>. You will have
to use a work-around, due to the fact that currently there is no
- <code>src/libhttpd.dll</code> build that is required to link against the
- shared module.</p>
+ <code>src/libhttpd.dll</code> (required to link against by the
+ shared module build process).</p>
-<li>Place an empty file to satisfy <code>make</code> and
+<li>Create an empty file to satisfy <code>make</code> and
restart the <code>make</code> process again:
<pre>
$ touch <i>/path/to/module.so</i>
@@ -251,18 +249,18 @@
$ make install
</pre>
<p>This will build the core dynamic library <code>libhttpd.dll</code> as
- described in the previous build alternative.</p>
+ described in the previous scenario.</p>
-<li> Now we have to link the shared module against that library:
+<li>Now we have to link the shared module against that library:
<pre>
$ cd <i>/path/to/module</i>
$ gcc --shared -o <i>module</i>.dll <i>module</i>.lo
<i>/path/to/libhttpd.dll</i>
</pre>
-<p>The build shared DLL module has to be placed to Apache's installation
- <code>bin</code>directory where <code>libhttpd.dll</code> goes too.</p>
+<p>The shared DLL module has to be placed in Apache's
+ <code>bin</code>directory, where <code>libhttpd.dll</code> also goes.</p>
<li>Add configuration directives to <code>conf/httpd.conf</code> to load
-and activate shared DLL modules while runtime:
+and activate shared DLL modules at runtime:
<pre>
# httpd.conf
[...]
@@ -274,30 +272,30 @@
</ul>
<p>The above steps have to be repeated for each shared DLL module you want
- to create.</p>
+ to build.</p>
<li><strong>Using apxs to create shared DLL modules</strong>
-<p>To make the extension process of your <code>httpd</code> using
- shared DLL modules easier you may use the
- <a href="programs/apxs.html"><code>apxs</code></a> tool.
+<p>To make the extending<code>httpd</code> with shared DLL modules
+ easier, you can use <a
+ href="programs/apxs.html"><code>apxs</code></a>.
<p>Make sure you have configured <code>$CFG_LDFLAGS_SHLIB</code> within
<code>apxs</code> to include the <code>--shared</code> directive and
the path to the shared code DLL <code>libhttpd.dll</code>.
<p>Now you should be able to create a shared DLL module from a
<code>mod_foo.c</code>
- source code file with:
+ source file with:
<pre>
$ apxs -c mod_foo.c -o mod_foo.dll
</pre>
- Place the created DLL file to Apache's <code>bin</code> directory, so
+ Place the resulting DLL in Apache's <code>bin</code> directory, so
the <code>dlopen()</code> function within the compiled in
<code>mod_so.c</code>
- module can find and load it while runtime.
+ module can find and load it at runtime.
</ul>
-<h2><a name="inst">Running Apache for Cygwin</a></h2>
+<h2><a name="run">Running Apache for Cygwin</a></h2>
<p>Apache on Cygwin can be started and stopped in the same manner
as on Unix systems. You may also use the
@@ -307,15 +305,15 @@
<ul>
<li><strong>Starting Apache</strong>
-<p>If installed to the default Apache layout directory you can start
+<p>If installed with the default Apache directory layout, you can start
<code>httpd</code> as follows:</p>
<pre>
$ /usr/local/apache/bin/httpd
</pre>
-<p>An explicit background <code>&</code> indicator is not required. The
- resulting parent process is detached from the current terminal.
- Check the global <code>error_log</code> to see if Apache has started
- cleanly without any major problems.</p>
+<p>An explicit background indicator (<code>&</code>) is not
+ required. The parent process is automatically detached from the
+ current terminal. Check the global <code>error_log</code> to see if
+ Apache started cleanly without any major problems.</p>
<li><strong>Stopping Apache</strong>
<p>To stop Apache send at least a <code>SIGTERM</code> signal to the
@@ -324,9 +322,9 @@
$ kill -TERM `cat /usr/local/apache/logs/httpd.pid`
</pre>
-<li><strong>Gracefully re-starting Apache</strong>
-<p>In order to update configuration directives and hence reload the given
- <code>httpd.conf</code> configuration file you may send a
<code>SIGHUP</code>
+<li><strong>Gracefully Restarting Apache</strong>
+<p>In order to update configuration directives and reload the
+ <code>httpd.conf</code> configuration file, send a <code>SIGHUP</code>
to the parent <code>httpd</code> process:
<pre>
$ kill -HUP `cat /usr/local/apache/logs/httpd.pid`
@@ -338,24 +336,25 @@
<h2><a name="serv">Running Apache for Cygwin as a Service</a></h2>
-<p>Apache on Cygwin can be invoked as Windows NT or Windows 2000 service.
+<p>Apache on Cygwin can be invoked as a Windows NT or Windows 2000 service.
Cygwin has its own <code>cygrunsrv.exe</code> facility to define, remove,
- start and stop services as follows:
+ start, and stop services as follows:
<ul>
<li><strong>Installing Apache as a new Service</strong>
-<p>Use the following statement to install the <code>httpd.exe</code> as a new
+<p>Use the following statement to install <code>httpd.exe</code> as a new
service:</p>
<pre>
$ cygrunsrv -I <i>service_name</i>-p /usr/local/apache/bin/httpd.exe [-a
<i>arguments</i>] \
[-e <i>VAR=VALUE</i>] [-t auto|manual] [-u <i>user</i>] [-w
<i>passwd</i>]
</pre>
-<p>Where <code>-a</code> is used to pass command line arguments to
- <code>httpd.exe</code>, like <code>-DFOO</code> defines and <code>-e</code>
- is used to pass environment variables to the starting environment. If
necessary
- you may use the <code>-t</code> options to set the starting type of the
service.
- If you want the new service to run under a different user you will have to
supply
- necessary arguments for the <code>-u</code> and <code>-w</code>
options.</p>
+<p>Where <code>-a</code> is used to pass command line arguments (such
+ as <code>-DFOO</code> defines) to <code>httpd.exe</code>, and
+ <code>-e</code> is used to pass environment variables. If necessary
+ you may use the <code>-t</code> options to set the autostart
+ configuration for the service. If you want the new service to run
+ under a different userid, you will have to supply the <code>-u</code>
+ and <code>-w</code> options.</p>
<li><strong>Starting Apache as a Service</strong>
<p>After the new service is installed it can be started using the following
@@ -366,7 +365,7 @@
<p>Check your process table and global <code>error_log</code> file to ensure
Apache
has started without any major problems.</p>
-<li><strong>Stopping Apache Service</strong>
+<li><strong>Stopping an Apache Service</strong>
<p>A running Apache service may be stopped using the following command:</p>
<pre>
$ cygrunsrv -E <i>service_name</i>
@@ -374,9 +373,8 @@
<p>This will stop all running <code>httpd.exe</code> processes and shutdown
the HTTP
service for the machine.</p>
-<li><strong>Removing Apache Service</strong>
-<p>An installed Apache service may be removed from the internal service
invocation
- table of Windows NT or Windows 2000 using the following command:</p>
+<li><strong>Removing an Apache Service</strong>
+<p>An installed Apache service may be removed from Windows NT or Windows
2000 using the following command:</p>
<pre>
$ cygrunsrv -R <i>service_name</i>
</pre>
@@ -384,8 +382,9 @@
</ul>
-<p>Please refer to the corresponding <code>man</code> page of
<code>cygrunsrv</code> and
- the Cygwin mailing list for further details of how services are
invoked.</p>
+<p>Please refer to the <code>man</code> page for <code>cygrunsrv</code>
+ and the Cygwin mailing list for further details of how services are
+ invoked.</p>
@@ -397,4 +396,3 @@
<!--#include virtual="footer.html" -->
</body>
</html>
-
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
