httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sl...@apache.org
Subject cvs commit: httpd-2.0/docs/manual dso.html
Date Wed, 19 Sep 2001 15:18:16 GMT
slive       01/09/19 08:18:16

  Modified:    docs/manual dso.html
  Log:
  Couple small updates to dso.html
  
  Revision  Changes    Path
  1.20      +14 -12    httpd-2.0/docs/manual/dso.html
  
  Index: dso.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/dso.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -d -b -u -r1.19 -r1.20
  --- dso.html	2001/09/19 14:49:34	1.19
  +++ dso.html	2001/09/19 15:18:16	1.20
  @@ -13,7 +13,7 @@
   >
   <!--#include virtual="header.html" -->
   
  -<H1>
  +<H1 align="center">
   Dynamic Shared Object (DSO) Support
   </H1>
   
  @@ -54,18 +54,20 @@
   
   <H2><a name="implementation">Implementation</a></H2>
   
  -<P>The DSO support for loading individual Apache modules is based on a module
  -named <A HREF="mod/mod_so.html"><CODE>mod_so.c</CODE></A> which
must be
  -statically compiled into the Apache core. It is the only module besides
  -<CODE>core.c</CODE> which cannot be put into a DSO itself.
  -Practically all other distributed Apache modules then can
  -then be placed into a DSO by individually enabling the DSO build for them via
  -<CODE>configure</CODE>'s <CODE>--enable-<i>module</i>=shared</CODE>
option 
  -(see top-level <CODE>INSTALL</CODE> file).  After a module is compiled into
  -a DSO named <CODE>mod_foo.so</CODE> you can use <A
  +<P>The DSO support for loading individual Apache modules is based on a
  +module named <A HREF="mod/mod_so.html"><CODE>mod_so.c</CODE></A>
which
  +must be statically compiled into the Apache core. It is the only
  +module besides <CODE>core.c</CODE> which cannot be put into a DSO
  +itself.  Practically all other distributed Apache modules then can
  +then be placed into a DSO by individually enabling the DSO build for
  +them via <CODE>configure</CODE>'s
  +<CODE>--enable-<i>module</i>=shared</CODE> option as disucussed
in the
  +<a href="install.html">install documentation</a>.  After a module is
  +compiled into a DSO named <CODE>mod_foo.so</CODE> you can use <A
   HREF="mod/mod_so.html"><CODE>mod_so</CODE></A>'s <A
  -HREF="mod/mod_so.html#loadmodule"><CODE>LoadModule</CODE></A> command
in your
  -<CODE>httpd.conf</CODE> file to load this module at server startup or restart.
  +HREF="mod/mod_so.html#loadmodule"><CODE>LoadModule</CODE></A> command
  +in your <CODE>httpd.conf</CODE> file to load this module at server
  +startup or restart.
   
   <P>To simplify this creation of DSO files for Apache modules
   (especially for third-party modules) a new support program named <a
  
  
  

Mime
View raw message