Commit 404cfefd authored by Ken Coar's avatar Ken Coar
Browse files 

	The semi-occasional partial cleaning-up of the HTML..


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

docs/manual/install-tpf.html

+157 −148
Original line number Diff line number Diff line 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<html>

<head>

<title>Installing Apache on TPF</title>

</head>

<HTML>

<HEAD>

<TITLE>Installing Apache on TPF</TITLE>

</HEAD>



<a name="top"></a>

<h1 align="center">Installing the Apache 1.3 HTTP Server on TPF</h1>

<hr>

<center>[&nbsp<a href="#setup">Setup</a>

   &nbsp|&nbsp<a href="#compilation">Compilation</a>

   &nbsp|&nbsp<a href="#installation">Installation</a>

   &nbsp|&nbsp<a href="#visualage">VisualAge</a>&nbsp]

</center>

<hr>

<br>

<BODY>

<H1 ALIGN="center">

 <A NAME="top">Installing the Apache 1.3 HTTP Server on TPF</A>

</H1>

<HR>

<CENTER>[&nbsp;<A HREF="#setup">Setup</A>

   &nbsp;|&nbsp;<A HREF="#compilation">Compilation</A>

   &nbsp;|&nbsp;<A HREF="#installation">Installation</A>

   &nbsp;|&nbsp;<A HREF="#visualage">VisualAge</A>&nbsp;]

</CENTER>

<HR>

<BR>



<p>

<P>

This document outlines the steps needed to install Apache onto a TPF system.

<br><br>

You should first read htdocs/manual/<a href="readme-tpf.html">readme-tpf.html</a>

</P>

<P>

You should first read

htdocs/manual/<A HREF="readme-tpf.html">readme-tpf.html</A>

for basic information on the port of Apache to TPF including required PUT level

and supported functions &amp; modules.

</p>

</P>



<a name="setup">&nbsp;</a>

<h2 align=center>Setup</h2>

<p>

Due to the use of EBCDIC on MVS OS/390 Open Edition (later referred to simply as

<H2 align=center><A NAME="setup">Setup</A></H2>

<P>

Due to the use of EBCDIC on MVS OS/390 Open Edition

(later referred to simply as

"Open Edition"), we've found that the most reliable

method for loading Apache onto your system is to unzip and tar the distribution

file on your PC, and then copy the extracted files to Open Edition via an NFS client

file on your PC, and then copy the extracted files to Open Edition

via an NFS client

capable of transferring the data in EBCDIC format.

<br><br>

</P>

<P>

Before moving the distribution to an

Open Edition environment, verify that the NFS drive will transfer the

filenames with upper/lower case preserved.

<br><br>

</P>

<P>

Since Open Edition is not the ultimate destination of the files,

the only required files and subdirectories that need to be moved to Open Edition

the only required files and subdirectories that need to be moved to

Open Edition

are in /src.

<br><br>

<font strong color=red>WARNING</font>:

</P>

<P>

<FONT COLOR=red><STRONG>WARNING</STRONG></FONT>:

If you are using a product such as WinZip on your PC, verify that

the <i>"TAR File Smart CR/LF Conversion"</i> option is NOT checked.

the <EM>"TAR File Smart CR/LF Conversion"</EM> option is NOT checked.

You can find this in WinZip under Options, Configuration.

Since you had to tar and unzip the file to read this document,

you need to re-tar and -unzip if the CR/LF option was checked.

This will save you lots of headaches later on.

<br><br>

<font strong color=red>WARNING</font>:

</P>

<P>

<FONT COLOR=red><STRONG>WARNING</STRONG></FONT>:

Editing files on a PC before moving them to Open Edition may result

in the loss/addition of unprintable characters.  Files of concern include shell

scripts and src/Configuration.  The most common problems are with tab characters

in the loss/addition of unprSintable characters.  Files of concern include shell

scripts and src/Configuration.  The most common problems are with

tab characters

and CR/LF characters.  Most editors will handle the CR/LF problem correctly

but none seem to handle tab characters.  If you need to edit files, edit them

in a UNIX editor such as vi or emacs.

</p>

</P>



<a name="compilation">&nbsp;</a>

<h2 align=center>Compilation</h2>

<p>

<H2 align=center><A NAME="compilation">Compilation</A></H2>

<P>

Apache supports the notion of "optional modules".  However,

the server has to know which modules are compiled into it.  In order for

those modules to be effective, it is necessary to generate a short bit of

code ("modules.c") which simply has a list of them. If you are using the

make and Configure utility, "modules.c" will be created for you.

<br><br>

</P>

<P>

The provided scripts assume a c89 compiler and have only been tested on an

Open Edition environment.  If you are using a platform other that

Open Edition you may need to modify src/os/tpf/TPFExport and src/Configure

to match your environment.

<br><br>

</P>

<P>

Note that UNIX/Open Edition commands in this section are shown in

<tt><strong>bold</strong></tt>,

<TT><STRONG>bold</STRONG></TT>,

are case sensitive, and must be made from the "src" directory.

<br><br>

<ol>

<li>Overlay src/Configuration with src/Configuration.tmpl:  

    <tt><strong>cp&nbsp;Configuration.tmpl&nbsp;Configuration</strong></tt>

    <br><br>

<li>Edit src/Configuration.  It contains the list and settings

</P>

<OL>

<LI>Overlay src/Configuration with src/Configuration.tmpl:  

    <TT><STRONG>cp&nbsp;Configuration.tmpl&nbsp;Configuration</STRONG></TT>

    <BR><BR>

<LI>Edit src/Configuration.  It contains the list and settings

    of various "Rules" and an additional section at the bottom that determines

    which modules to compile:

    <br><br>

    <ol type=a>

    <li>Adjust the Rules and <tt>EXTRA_CFLAGS|LIBS|LDFLAGS|INCLUDES</tt>

    <BR><BR>

    <OL type=a>

    <LI>Adjust the Rules and <TT>EXTRA_CFLAGS|LIBS|LDFLAGS|INCLUDES</TT>

        if you feel so inclined.

    <br><br>

    <li>Comment out (by preceding the line with a "#") lines corresponding

    <BR><BR>

    <LI>Comment out (by preceding the line with a "#") lines corresponding

        to those modules you DO&nbsp;NOT wish to include.

        At present the following modules MUST be commented out

        as they are not yet supported on TPF: mod_actions, mod_auth,

        mod_cgi, mod_env, mod_include, & mod_status.

    <br><br>

    <li>Uncomment (by removing the initial "#", if present) lines

    <BR><BR>

    <LI>Uncomment (by removing the initial "#", if present) lines

        corresponding to those optional modules you wish

        to include or add new lines corresponding to any custom modules

        you have written.

        The htdocs/manual/<a href="readme-tpf.html">readme-tpf.html</a>

        The htdocs/manual/<A HREF="readme-tpf.html">readme-tpf.html</A>

        document lists the modules that have been tested on TPF.

    </ol>

    <br>

<li>Set the TPF environment variables:

    <tt><strong>.&nbsp;os/tpf/TPFExport</strong></tt>

    <br>

    </OL>

    <BR>

<LI>Set the TPF environment variables:

    <TT><STRONG>.&nbsp;os/tpf/TPFExport</STRONG></TT>

    <BR>

    (The initial period and blank on the command are required to ensure

    the environment variables exist beyond the scope of the shell script.)

    This script will set the environment variables required to compile the
@@ -111,14 +123,14 @@ are case sensitive, and must be made from the "src" directory. 
    installation, in particular, the system include file directories.  The

    system include files must reside on your Open Edition system in the

    appropriate file structure similar to /usr/include and /usr/include/sys.

    DO&nbsp;NOT modify the <tt>TPF=YES</tt> export variable.  If this is changed, the

    "Configure" script will not recognize TPF.

    <br><br>

<li>Run the "Configure" script:

    <tt><strong>Configure</strong></tt>

    <br>

    DO&nbsp;NOT modify the <TT>TPF=YES</TT> export variable.  If this is

    changed, the "Configure" script will not recognize TPF.

    <BR><BR>

<LI>Run the "Configure" script:

    <TT><STRONG>Configure</STRONG></TT>

    <BR>

    The output will look something like this...

      <pre>

      <PRE>

      Using config file: Configuration

      Creating Makefile

       + configured for TPF platform
@@ -134,134 +146,131 @@ are case sensitive, and must be made from the "src" directory. 
      Creating Makefile in modules/standard

      Creating Makefile in modules/example

      $ _

      </pre>

      </PRE>

    This generates modules.c and new versions of the Makefiles.

    <br><br>

    If you want to maintain multiple configurations, you can say, e.g.,

    <br>

    <tt><strong>Configure -file Configuration.ai</strong></tt>

    <br>

      <pre>

    <BR><BR>

    If you want to maintain multiple configurations, you can

    say, <EM>e.g.</EM>,

    <BR>

    <TT><STRONG>Configure -file Configuration.ai</STRONG></TT>

    <BR>

      <PRE>

      Using config file: Configuration.ai

      Creating Makefile

       + configured for &lt;whatever&gt; platform

       + setting C compiler to &lt;whatever&gt;

      et cetera

      </pre>

      </PRE>



    If you receive an error such as "<tt>Configure 146: FSUM7351 not found</tt>"

    If you receive an error such as "<TT>Configure 146: FSUM7351 not found</TT>"

    the most likely explanation is that one or more of the make related

    files were edited on a non-UNIX platform, corrupting the end-of-line marks.

    Verify that lines ending with "\" in the flagged file do&nbsp;not have trailing

    spaces.  Using the vi editor and the sample error above as an example...

    <br><br><pre>

            pull up the flagged file:       <strong>vi&nbsp;Configure</strong>

            turn on punctuation:            <strong>:set&nbsp;list</strong>

            go to the line in question:     <strong>146G</strong>

               or find a line with a "\":   <strong>/\\</strong></pre>

    The end of line should display as "<tt>\$</tt>".  If it is displayed as

    "<tt>\ $</tt>" (with a blank between \ and $) then you should revert to the

    <BR><BR><PRE>

            pull up the flagged file:       <STRONG>vi&nbsp;Configure</STRONG>

            turn on punctuation:            <STRONG>:set&nbsp;list</STRONG>

            go to the line in question:     <STRONG>146G</STRONG>

               or find a line with a "\":   <STRONG>/\\</STRONG></PRE>

    The end of line should display as "<TT>\$</TT>".  If it is displayed as

    "<TT>\ $</TT>" (with a blank between \ and $) then you should revert to the

    distributed version of the file and make the site-specific

    changes again using a UNIX compatible editor such as vi or emacs.

    Then try the Configure command again.

    <br><pre>            close the file:                 <strong>:q  </strong>(or 

    <BR><PRE>            close the file:                 <STRONG>:q  </STRONG>(or 



<strong>:quit!</strong>)</pre>

<li>Now compile the programs: <tt><strong>make</strong></tt><br>

<STRONG>:quit!</STRONG>)</PRE>

<LI>Now compile the programs: <TT><STRONG>make</STRONG></TT><BR>

    The modules placed in the Apache distribution are the ones that have been

    tested and are used regularly by various members of the Apache development

    group.  Additional modules contributed by members or third parties with specific

    needs or functions are available at

    <a 



href="http://www.apache.org/dist/contrib/modules/">http://www.apache.org/dist/contrib/modules/</a



>.

    <A 

HREF="http://www.apache.org/dist/contrib/modules/">http://www.apache.org/dist/contrib/modules/</A>.

    There are instructions on that page for linking these modules into the core Apache

    code.

    <br><br>

    <BR><BR>

    If during compilation you get a warning about a missing 'regex.h', set

    <tt>WANTHSREGEX=yes</tt> in the src/Configuration file and start back at the

    <tt><strong>Configure</strong></tt> step.

</ol>

</p>

    <TT>WANTHSREGEX=yes</TT> in the src/Configuration file and start back at the

    <TT><STRONG>Configure</STRONG></TT> step.

</OL>



<a name="installation">&nbsp;</a>

<h2 align=center>Installation</h2>

<ol>

<li>After compilation, you will have all the object files required to build an

<A NAME="installation">&nbsp;</A>

<H2 align=center>Installation</H2>

<OL>

<LI>After compilation, you will have all the object files required to build an

  "httpd" loadset.  The next step is to link the object files and create a loadset to be

  stored in a PDS.  Sample JCL for linking and loadsets has been included in

  src/os/tpf/samples as "linkdll.jcl" and "loadset.jcl".  You can submit these jobs

  from CMS or directly from Open Edition if you have the proper authority.  After

  the jobs have completed, you can <tt>ZOLDR LOAD</tt> them to your TPF system.

  <br><br>

  NOTE: The <tt>mod_<i>xxx</i>.o</tt> files in the linkdll.jcl file must correspond to the

  <tt>mod_<i>xxx</i>.o</tt> lines in the src/Configuration file.

  <br><br>

<li>

  the jobs have completed, you can <TT>ZOLDR LOAD</TT> them to your TPF system.

  <BR><BR>

  NOTE: The <TT>mod_<EM>xxx</EM>.o</TT> files in the linkdll.jcl file must correspond to the

  <TT>mod_<EM>xxx</EM>.o</TT> lines in the src/Configuration file.

  <BR><BR>

<LI>

  Apache requires a configuration file to initialize itself during activation.

  (Previously three configuration files were used.)

  Copy the distribution version, /conf/httpd.conf-dist, to /conf/httpd.conf and then

  edit the /conf/httpd.conf copy with your site specific information.  This first release

  of Apache for TPF only runs under the "inetd" model so you

  <font strong color=red>must</font> change <tt>ServerType</tt> from <tt>standalone</tt>

  to <tt>inetd</tt>.

  <br><br>

  <font color=red><STRONG>must</STRONG></FONT> change <TT>ServerType</TT> from <TT>standalone</TT>

  to <TT>inetd</TT>.

  <BR><BR>

  General documentation for Apache is located at

  <a href="http://www.apache.org/docs/">http://www.apache.org/docs/</a>

  <A HREF="http://www.apache.org/docs/">http://www.apache.org/docs/</A>

  and in the HTML pages included with this distribution under the

  /htdocs/manual directory.

  <br><br>

<li>On TPF activate ZCLAW and update INETD using ZINET entries, the common case:

    <br><br>

    <pre>

  <BR><BR>

<LI>On TPF activate ZCLAW and update INETD using ZINET entries, the common case:

    <BR><BR>

    <PRE>

    ZINET ADD S-TFTP   PGM-CTFT PORT-69 PROTOCOL-UDP MODEL-NOWAIT

    ZINET ADD S-APACHE PGM-<i>pppp</i> PORT-80 PROTOCOL-TCP MODEL-NOWAIT</pre>

  Please refer to <i>IBM Transaction Processing Facility Transmission Control

  Protocol/Internet Protocol Version 4 Release 1</i> for more information

    ZINET ADD S-APACHE PGM-<EM>pppp</EM> PORT-80 PROTOCOL-TCP MODEL-NOWAIT</PRE>

  Please refer to <EM>IBM Transaction Processing Facility Transmission Control

  Protocol/Internet Protocol Version 4 Release 1</EM> for more information

  on ZCLAW, INETD, and TFTP.

  <br><br>

<li>Prior to sending a request to your Apache server from a browser,

  <BR><BR>

<LI>Prior to sending a request to your Apache server from a browser,

    TFTP the configuration file, log, icons and web pages to your TPF system.

    A typical directory structure for Apache is as follows:

<pre>     /usr/local/apache/conf

<PRE>     /usr/local/apache/conf

     /usr/local/apache/logs

     /usr/local/apache/icons

     /usr/local/apache/htdocs</pre>

     /usr/local/apache/htdocs</PRE>

    The logs directory must exist in order to avoid an

    <code>fopen</code> error while running Apache.  TFTP an empty file into

    <CODE>fopen</CODE> error while running Apache.  TFTP an empty file into

    the logs subdirectory to create it.  All gif, jpg, and zip files should be

    TFTP'd as binary; conf files and html pages should be TFTP'd as text.

</ol>

<a name="visualage">&nbsp;</a>

<h2 align=center>Compiling with VisualAge TPF</h2>

<p>

</OL>

<A NAME="visualage">&nbsp;</A>

<H2 align=center>Compiling with VisualAge TPF</H2>

<P>

  It is not required that "make" be used to compile Apache for TPF:

  Individual programs may be compiled using IBM's VisualAge TPF product.

  This is particularly useful when compiling selected programs for the Debug Tool.

  <br><br>

  <BR><BR>

  The following VisualAge compile settings are required:

  <ul>

  <li><i>"DEFINE - Define preprocessor macro name(s)"</i> must include

     <tt><strong>TPF, CHARSET_EBCDIC, _POSIX_SOURCE,</strong></tt> and

     <tt><strong>USE_HSREGEX</strong></tt>

  <br><br>

  <li><i>"LSEARCH - Path for user include files"</i> must include

     <tt><strong>../src/include</strong></tt> and <tt><strong>../src/os/tpf</strong></tt>

  <br><br>

  <li><i>"DLL - Generate DLL code"</i> must be checked

  <br><br>

  <li><i>"LONGNAME - Support long names"</i> must be checked

  </ul>

</p>

<hr>

<center>[&nbsp<a href="#top">top</a>

   &nbsp|&nbsp<a href="#setup">Setup</a>

   &nbsp|&nbsp<a href="#compilation">Compilation</a>

   &nbsp|&nbsp<a href="#installation">Installation</a>

   &nbsp|&nbsp<a href="#visualage">VisualAge</a>&nbsp]

</center>

  <UL>

  <LI><EM>"DEFINE - Define preprocessor macro name(s)"</EM> must include

     <TT><STRONG>TPF, CHARSET_EBCDIC, _POSIX_SOURCE,</STRONG></TT> and

     <TT><STRONG>USE_HSREGEX</STRONG></TT>

  <BR><BR>

  <LI><EM>"LSEARCH - Path for user include files"</EM> must include

     <TT><STRONG>../src/include</STRONG></TT> and <TT><STRONG>../src/os/tpf</STRONG></TT>

  <BR><BR>

  <LI><EM>"DLL - Generate DLL code"</EM> must be checked

  <BR><BR>

  <LI><EM>"LONGNAME - Support long names"</EM> must be checked

  </UL>

</P>

<HR>

<CENTER>[&nbsp;<A HREF="#top">top</A>

   &nbsp;|&nbsp;<A HREF="#setup">Setup</A>

   &nbsp;|&nbsp;<A HREF="#compilation">Compilation</A>

   &nbsp;|&nbsp;<A HREF="#installation">Installation</A>

   &nbsp;|&nbsp;<A HREF="#visualage">VisualAge</A>&nbsp;]

</CENTER>



</body>

</html>
 
</BODY>

</HTML>

docs/manual/mod/mod_mime.html

+1 −1
Original line number Diff line number Diff line
@@ -51,7 +51,7 @@ copies may still be used by a client or proxy, with the previous headers. 
<H2><A NAME="multipleext">Files with Multiple Extensions</A></H2>



Files can have more than one extension, and the order of the

extensions is <i>normally</i> irrelevant. For example, if the file

extensions is <EM>normally</EM> irrelevant. For example, if the file

<CODE>welcome.html.fr</CODE> maps onto content type text/html and

language French then the file <CODE>welcome.fr.html</CODE> will map

onto exactly the same information. The only exception to this is if an

docs/manual/platform/readme-tpf.html

+168 −168

File changed.

Preview size limit exceeded, changes collapsed.

docs/manual/suexec.html

+9 −9
Original line number Diff line number Diff line
@@ -309,25 +309,25 @@ for Apache 1.3 with the AutoConf-style interface (APACI). 
    activated by default. At least one --suexec-xxxxx option has to be

    provided together with the --enable-suexec option to let APACI

    accept your request for using the suEXEC feature.

<DT><CODE>--suexec-caller=<I>UID</I></CODE>

<DT><CODE>--suexec-caller=<EM>UID</EM></CODE>

<DD>The <A HREF="mod/core.html#user">username</A> under which

    Apache normally runs.

    This is the only user allowed to execute this program.

<DT><CODE>--suexec-docroot=<I>DIR</I></CODE>

<DT><CODE>--suexec-docroot=<EM>DIR</EM></CODE>

<DD>Define as the DocumentRoot set for Apache.

    This will be the only hierarchy (aside from UserDirs)

    that can be used for suEXEC behavior.

    The default directory is the --datadir value with 

    the suffix "/htdocs", e.g. if you configure with

    the suffix "/htdocs", <EM>e.g.</EM> if you configure with

    "<CODE>--datadir=/home/apache</CODE>" the directory

    "/home/apache/htdocs" is used as document root for

    the suEXEC wrapper.

<DT><CODE>--suexec-logfile=<I>FILE</I></CODE>

<DT><CODE>--suexec-logfile=<EM>FILE</EM></CODE>

<DD>This defines the filename to which all suEXEC transactions and

    errors are logged (useful for auditing and debugging purposes).

    By default the logfile is named "suexec_log" and located in your

    standard logfile directory (--logfiledir).

<DT><CODE>--suexec-userdir=<I>DIR</I></CODE>

<DT><CODE>--suexec-userdir=<EM>DIR</EM></CODE>

<DD>Define to be the subdirectory under users'

    home directories where suEXEC access should

    be allowed.  All executables under this directory
@@ -346,15 +346,15 @@ for Apache 1.3 with the AutoConf-style interface (APACI). 
    all reside in one parent directory; then name that

    parent directory here.  <STRONG>If this is not defined

    properly, "~userdir" cgi requests will not work!</STRONG>

<DT><CODE>--suexec-uidmin=<I>UID</I></CODE>

<DT><CODE>--suexec-uidmin=<EM>UID</EM></CODE>

<DD>Define this as the lowest UID allowed to be a target user

    for suEXEC.  For most systems, 500 or 100 is common.

    Default value is 100.

<DT><CODE>--suexec-gidmin=<I>GID</I></CODE>

<DT><CODE>--suexec-gidmin=<EM>GID</EM></CODE>

<DD>Define this as the lowest GID allowed to be a target group

    for suEXEC. For most systems, 100 is common and therefore

    used as default value.

<DT><CODE>--suexec-safepath=<I>PATH</I></CODE>

<DT><CODE>--suexec-safepath=<EM>PATH</EM></CODE>

<DD>Define a safe PATH environment to pass to CGI executables.

    Default value is "/usr/local/bin:/usr/bin:/bin".

</DL>
@@ -407,7 +407,7 @@ directory (default is "/usr/local/apache/sbin/suexec"). 
If Apache finds a properly configured suEXEC wrapper, it will print

the following message to the error log:

<PRE>

    [notice] suEXEC mechanism enabled (wrapper: <I>/path/to/suexec</I>)

    [notice] suEXEC mechanism enabled (wrapper: <EM>/path/to/suexec</EM>)

</PRE>

If you don't see this message at server startup, the server is most

likely not finding the wrapper program where it expects it, or the

docs/manual/suexec.html.en

+9 −9
Original line number Diff line number Diff line
@@ -309,25 +309,25 @@ for Apache 1.3 with the AutoConf-style interface (APACI). 
    activated by default. At least one --suexec-xxxxx option has to be

    provided together with the --enable-suexec option to let APACI

    accept your request for using the suEXEC feature.

<DT><CODE>--suexec-caller=<I>UID</I></CODE>

<DT><CODE>--suexec-caller=<EM>UID</EM></CODE>

<DD>The <A HREF="mod/core.html#user">username</A> under which

    Apache normally runs.

    This is the only user allowed to execute this program.

<DT><CODE>--suexec-docroot=<I>DIR</I></CODE>

<DT><CODE>--suexec-docroot=<EM>DIR</EM></CODE>

<DD>Define as the DocumentRoot set for Apache.

    This will be the only hierarchy (aside from UserDirs)

    that can be used for suEXEC behavior.

    The default directory is the --datadir value with 

    the suffix "/htdocs", e.g. if you configure with

    the suffix "/htdocs", <EM>e.g.</EM> if you configure with

    "<CODE>--datadir=/home/apache</CODE>" the directory

    "/home/apache/htdocs" is used as document root for

    the suEXEC wrapper.

<DT><CODE>--suexec-logfile=<I>FILE</I></CODE>

<DT><CODE>--suexec-logfile=<EM>FILE</EM></CODE>

<DD>This defines the filename to which all suEXEC transactions and

    errors are logged (useful for auditing and debugging purposes).

    By default the logfile is named "suexec_log" and located in your

    standard logfile directory (--logfiledir).

<DT><CODE>--suexec-userdir=<I>DIR</I></CODE>

<DT><CODE>--suexec-userdir=<EM>DIR</EM></CODE>

<DD>Define to be the subdirectory under users'

    home directories where suEXEC access should

    be allowed.  All executables under this directory
@@ -346,15 +346,15 @@ for Apache 1.3 with the AutoConf-style interface (APACI). 
    all reside in one parent directory; then name that

    parent directory here.  <STRONG>If this is not defined

    properly, "~userdir" cgi requests will not work!</STRONG>

<DT><CODE>--suexec-uidmin=<I>UID</I></CODE>

<DT><CODE>--suexec-uidmin=<EM>UID</EM></CODE>

<DD>Define this as the lowest UID allowed to be a target user

    for suEXEC.  For most systems, 500 or 100 is common.

    Default value is 100.

<DT><CODE>--suexec-gidmin=<I>GID</I></CODE>

<DT><CODE>--suexec-gidmin=<EM>GID</EM></CODE>

<DD>Define this as the lowest GID allowed to be a target group

    for suEXEC. For most systems, 100 is common and therefore

    used as default value.

<DT><CODE>--suexec-safepath=<I>PATH</I></CODE>

<DT><CODE>--suexec-safepath=<EM>PATH</EM></CODE>

<DD>Define a safe PATH environment to pass to CGI executables.

    Default value is "/usr/local/bin:/usr/bin:/bin".

</DL>
@@ -407,7 +407,7 @@ directory (default is "/usr/local/apache/sbin/suexec"). 
If Apache finds a properly configured suEXEC wrapper, it will print

the following message to the error log:

<PRE>

    [notice] suEXEC mechanism enabled (wrapper: <I>/path/to/suexec</I>)

    [notice] suEXEC mechanism enabled (wrapper: <EM>/path/to/suexec</EM>)

</PRE>

If you don't see this message at server startup, the server is most

likely not finding the wrapper program where it expects it, or the