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.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@79972 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/misc/FAQ.html b/docs/manual/misc/FAQ.html
index 93ebbc65184779e630732cf57ddc0c2f05a9f018..cd9e6c476a45c5eec54bfc13bb174dfc76fe93cb 100644 (file)
--- a/docs/manual/misc/FAQ.html
+++ b/docs/manual/misc/FAQ.html
@@ -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

diff --git a/docs/manual/mod/index.html b/docs/manual/mod/index.html
index 2641092cea416111a6935d065ea122303a2dbd5c..426e7758f2692c30fa2b4b7831cd926cd8b2dd08 100644 (file)
--- a/docs/manual/mod/index.html
+++ b/docs/manual/mod/index.html
@@ -42,8 +42,6 @@ Apache distribution.  See also the complete alphabetical list of
 <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

diff --git a/docs/manual/mod/mod_auth.html b/docs/manual/mod/mod_auth.html
index c2db0344d13079a73c92be4bffb6157685af0a93..c0286fe39517ae62b74429f1c4a31831f781d2f5 100644 (file)
--- a/docs/manual/mod/mod_auth.html
+++ b/docs/manual/mod/mod_auth.html
@@ -115,8 +115,8 @@ regardless of the AuthAuthoritative setting.
 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

diff --git a/docs/manual/mod/mod_auth_anon.html b/docs/manual/mod/mod_auth_anon.html
index 5e61f34af204a9b81c0f7cef4156834f44f7e400..2ab6e88afabc3e6d9bcc13d5bc1eecdb9fba9ed4 100644 (file)
--- a/docs/manual/mod/mod_auth_anon.html
+++ b/docs/manual/mod/mod_auth_anon.html
@@ -156,7 +156,7 @@ allows users to share URLs.
 <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>