httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@hyperreal.org
Subject cvs commit: apachen/htdocs/manual/mod index.html mod_auth.html mod_auth_anon.html mod_auth_msql.html
Date Fri, 23 Jan 1998 16:13:58 GMT
coar        98/01/23 08:13:58

  Modified:    htdocs/manual/misc FAQ.html
               htdocs/manual/mod index.html mod_auth.html
                        mod_auth_anon.html
  Removed:     htdocs/manual/mod mod_auth_msql.html
  Log:
  	mod_auth_msql isn't part of the distribution any more, so take
  	out all references to it that assume it is.  Plus some miscellaneous
  	HTML cleanup.
  
  Revision  Changes    Path
  1.100     +7 -6      apachen/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.99
  retrieving revision 1.100
  diff -u -r1.99 -r1.100
  --- FAQ.html	1998/01/23 00:36:30	1.99
  +++ FAQ.html	1998/01/23 16:13:50	1.100
  @@ -15,7 +15,7 @@
     <!--#include virtual="header.html" -->
     <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
     <P>
  -  $Revision: 1.99 $ ($Date: 1998/01/23 00:36:30 $)
  +  $Revision: 1.100 $ ($Date: 1998/01/23 16:13:50 $)
     </P>
     <P>
     The latest version of this FAQ is always available from the main
  @@ -1803,11 +1803,12 @@
     <A HREF="http://www.linuxhq.com/HOWTO/META-FAQ.html"
     >Linux newsgroup/mailing list</A>.
     As a last-resort workaround, you can
  -  comment out the <CODE>#define USE_SHMGET_SCOREBOARD</CODE> definition in
the
  +  comment out the <CODE>#define&nbsp;USE_SHMGET_SCOREBOARD</CODE>
  +  definition in the
     <SAMP>LINUX</SAMP> section of
     <SAMP>src/conf.h</SAMP> and rebuild the server (prior to 1.3b4, simply
  -  removing <CODE>#define HAVE_SHMGET</CODE> would have sufficed).  This will
  -  produce a server which is slower and less reliable.
  +  removing <CODE>#define&nbsp;HAVE_SHMGET</CODE> would have sufficed).
  +  This will produce a server which is slower and less reliable.
     </P>
     <HR>
    </LI>
  @@ -1892,8 +1893,8 @@
        </A>
     <P>
     You have probably configured the Host by specifying a FQHN,
  -  and thus the libmsql will use a full blown tcp/ip socket to talk to
  -  the database, rather than a fast internal device.  The
  +  and thus the <SAMP>libmsql</SAMP> will use a full blown TCP/IP socket
  +  to talk to the database, rather than a fast internal device.  The
     <SAMP>libmsql</SAMP>, the mSQL FAQ, and the <SAMP>mod_auth_msql</SAMP>
     documentation warn you about this.  If you have to use different
     hosts, check out the <SAMP>mod_auth_msql</SAMP> code for
  
  
  
  1.22      +0 -2      apachen/htdocs/manual/mod/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/mod/index.html,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- index.html	1997/10/24 09:34:21	1.21
  +++ index.html	1998/01/23 16:13:56	1.22
  @@ -42,8 +42,6 @@
   <dd>User authentication using Berkeley DB files.
   <dt><A HREF="mod_auth_dbm.html">mod_auth_dbm</A>
   <dd>User authentication using DBM files.
  -<dt><A HREF="mod_auth_msql.html">mod_auth_msql</A> Apache 1.2.* and earlier
  -<dd>User authentication using mSQL files.
   <dt><A HREF="mod_autoindex.html">mod_autoindex</A>
   <dd>Automatic directory listings.
   <dt><A HREF="mod_browser.html">mod_browser</A> Apache 1.2.* only
  
  
  
  1.10      +2 -2      apachen/htdocs/manual/mod/mod_auth.html
  
  Index: mod_auth.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/mod/mod_auth.html,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- mod_auth.html	1997/12/16 20:57:38	1.9
  +++ mod_auth.html	1998/01/23 16:13:56	1.10
  @@ -115,8 +115,8 @@
   A common use for this is in conjunction with one of the database
   modules; such as <a
   href="mod_auth_db.html"><code>mod_auth_db.c</code></a>, <a
  -href="mod_auth_dbm.html"><code>mod_auth_dbm.c</code></a>, <a
  -href="mod_auth_msql.html"><code>mod_auth_msql.c</code></a> and <a
  +href="mod_auth_dbm.html"><code>mod_auth_dbm.c</code></a>, 
  +<code>mod_auth_msql.c</code>, and <a
   href="mod_auth_anon.html"><code>mod_auth_anon.c</code></a>. These
modules
   supply the bulk of the user credential checking; but a few
   (administrator) related accesses fall through to a lower level with a
  
  
  
  1.15      +1 -1      apachen/htdocs/manual/mod/mod_auth_anon.html
  
  Index: mod_auth_anon.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/mod/mod_auth_anon.html,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- mod_auth_anon.html	1997/09/16 04:06:03	1.14
  +++ mod_auth_anon.html	1998/01/23 16:13:57	1.15
  @@ -156,7 +156,7 @@
   <h2><a name="Example">Example</A></h2>
   
   The example below (when combined with the Auth directives
  -of a htpasswd-file based (or GDM, mSQL etc) base access
  +of a htpasswd-file based (or GDM, mSQL <EM>etc.</EM>) base access
   control system allows users in as 'guests' with the
   following properties:
   <ul>
  
  
  

Mime
View raw message