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 invoking.xml invoking.html.en
Date Thu, 15 Aug 2002 22:47:26 GMT
slive       2002/08/15 15:47:26

  Modified:    docs/manual invoking.html.en
  Added:       docs/manual invoking.xml
  Log:
  New XML.
  
  Revision  Changes    Path
  1.36      +32 -80    httpd-2.0/docs/manual/invoking.html.en
  
  Index: invoking.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/invoking.html.en,v
  retrieving revision 1.35
  retrieving revision 1.36
  diff -u -d -b -u -r1.35 -r1.36
  --- invoking.html.en	25 Jul 2002 21:46:38 -0000	1.35
  +++ invoking.html.en	15 Aug 2002 22:47:26 -0000	1.36
  @@ -1,79 +1,42 @@
  -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  -    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  -
  -<html xmlns="http://www.w3.org/1999/xhtml">
  -  <head>
  -    <meta name="generator" content="HTML Tidy, see www.w3.org" />
  -
  -    <title>Starting Apache</title>
  -  </head>
  -  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  -
  -  <body bgcolor="#FFFFFF" text="#000000" link="#0000FF"
  -  vlink="#000080" alink="#FF0000">
  -    <!--#include virtual="header.html" -->
  -
  -    <h1 align="center">Starting Apache</h1>
  -
  -    <ul>
  -      <li><a href="#windows">Starting Apache on Windows</a></li>
  -
  -      <li>
  -        <a href="#unix">Starting Apache on Unix</a> 
  -
  -        <ul>
  -          <li><a href="#errors">Errors During Start-up</a></li>
  -
  -          <li><a href="#boot">Starting at Boot-Time</a></li>
  -
  -          <li><a href="#info">Additional Information</a></li>
  -        </ul>
  -      </li>
  -    </ul>
  -    <hr />
  -
  -    <h2><a id="windows" name="windows">Starting Apache On
  -    Windows</a></h2>
  -
  +<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><!--
  +        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  +              This file is generated from xml source: DO NOT EDIT
  +        XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  +      --><title>Starting Apache - Apache HTTP Server</title><link href="./style/manual.css"
type="text/css" rel="stylesheet"></head><body><blockquote><div align="center"><img
src="./images/sub.gif" alt="[APACHE DOCUMENTATION]"><h3>Apache HTTP Server Version
2.0</h3></div><h1 align="center">Starting Apache</h1>
       <p>On Windows, Apache is normally run as a service on Windows
       NT, or as a console application on Windows 95. For details, see
       <a href="platform/windows.html#run">running Apache for
       Windows</a>.</p>
   
  -    <h2><a id="unix" name="unix">Starting Apache on Unix</a></h2>
  -
       <p>On Unix, the <a href="programs/httpd.html">httpd</a> program
  -    is run as a daemon which executes continuously in the
  -    background to handle requests.</p>
  +    is run as a daemon that executes continuously in the
  +    background to handle requests.  This document describes how
  +    to invoke <code>httpd</code>.</p>
  +<ul><li><a href="#startup">How Apache Starts</a></li><li><a
href="#errors">Errors During Start-up</a></li><li><a href="#boot">Starting
at Boot-Time</a></li><li><a href="#info">Additional Information</a></li></ul><hr><h2><a
name="startup">How Apache Starts</a></h2>
   
  -    <p>If the <a href="mod/mpm_common.html#Listen">Listen</a> specified
in
  -    the configuration file is default of 80 (or any other port
  -    below 1024), then it is necessary to have root privileges in
  +    <p>If the <a href="./mod/mpm_common.html#listen" class="directive"><code
class="directive">Listen</code></a>
  +    specified in the configuration file is default of 80 (or any other
  +    port below 1024), then it is necessary to have root privileges in
       order to start apache, so that it can bind to this privileged
  -    port. Once the server has started and performed a few
  -    preliminary activities such as opening its log files, it will
  -    launch several <em>child</em> processes which do the work of
  -    listening for and answering requests from clients. The main
  -    <code>httpd</code> process continues to run as the root user,
  -    but the child processes run as a less privileged user. This is
  -    controlled by the selected <a href="mpm.html">Multi-Processing
  -    Module</a>.</p>
  +    port. Once the server has started and performed a few preliminary
  +    activities such as opening its log files, it will launch several
  +    <em>child</em> processes which do the work of listening for and
  +    answering requests from clients. The main <code>httpd</code>
  +    process continues to run as the root user, but the child processes
  +    run as a less privileged user. This is controlled by the selected
  +    <a href="mpm.html">Multi-Processing Module</a>.</p>
   
       <p>The first thing that <code>httpd</code> does when it is
  -    invoked is to locate and read the <a
  -    href="configuring.html">configuration file</a>
  +    invoked is to locate and read the <a href="configuring.html">configuration file</a>
       <code>httpd.conf</code>. The location of this file is set at
       compile-time, but it is possible to specify its location at run
       time using the <code>-f</code> command-line option as in</p>
   
  -    <blockquote>
  -      <code>/usr/local/apache/bin/httpd -f
  -      /usr/local/apache/conf/httpd.conf</code>
  -    </blockquote>
  +<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>/usr/local/apache/bin/httpd
-f
  +      /usr/local/apache/conf/httpd.conf</code></td></tr></table></blockquote>
   
       <p>As an alternative to invoking the <code>httpd</code> binary
  -    directly, a shell script called <a
  -    href="programs/apachectl.html">apachectl</a> is provided which
  +    directly, a shell script called <a href="programs/apachectl.html">apachectl</a>
is provided which
       can be used to control the daemon process with simple commands
       such as <code>apachectl start</code> and <code>apachectl
       stop</code>.</p>
  @@ -82,17 +45,14 @@
       the terminal and the command prompt will return almost
       immediately. This indicates that the server is up and running.
       You can then use your browser to connect to the server and view
  -    the test page in the <a
  -    href="mod/core.html#documentroot">DocumentRoot</a> directory
  +    the test page in the <a href="./mod/core.html#documentroot" class="directive"><code
class="directive">DocumentRoot</code></a> directory
       and the local copy of the documentation linked from that
       page.</p>
  -
  -    <h3><a id="errors" name="errors">Errors During
  -    Start-up</a></h3>
  +<h2><a name="errors">Errors During Start-up</a></h2>
   
       <p>If Apache suffers a fatal problem during startup, it will
       write a message describing the problem either to the console or
  -    to the <a href="mod/core.html#errorlog">ErrorLog</a> before
  +    to the <a href="./mod/core.html#errorlog" class="directive"><code class="directive">ErrorLog</code></a>
before
       exiting. One of the most common error messages is "<code>Unable
       to bind to Port ...</code>". This message is usually caused by
       either:</p>
  @@ -108,8 +68,7 @@
   
       <p>For further trouble-shooting instructions, consult the
       Apache <a href="faq/">FAQ</a>.</p>
  -
  -    <h3><a id="boot" name="boot">Starting at Boot-Time</a></h3>
  +<h2><a name="boot">Starting at Boot-Time</a></h2>
   
       <p>If you want your server to continue running after a system
       reboot, you should add a call to <code>httpd</code> or
  @@ -121,19 +80,12 @@
       designed so that it can often be linked directly as an init
       script, but be sure to check the exact requirements of your
       system.</p>
  +<h2><a name="info">Additional Information</a></h2>
   
  -    <h3><a id="info" name="info">Additional Information</a></h3>
  -
  -    <p>Additional information about the command-line options of <a
  -    href="programs/httpd.html">httpd</a> and <a
  -    href="programs/apachectl.html">apachectl</a> as well as other
  +    <p>Additional information about the command-line options of <a href="programs/httpd.html">httpd</a>
and <a href="programs/apachectl.html">apachectl</a> as well as other
       support programs included with the server is available on the
       <a href="programs/">Server and Supporting Programs</a> page.
  -    There is also documentation on all the <a
  -    href="mod/">modules</a> included with the Apache distribution
  +    There is also documentation on all the <a href="mod/">modules</a> included
with the Apache distribution
       and the <a href="mod/directives.html">directives</a> that they
       provide.</p>
  -    <!--#include virtual="footer.html" -->
  -  </body>
  -</html>
  -
  +<hr></blockquote><h3 align="center">Apache HTTP Server Version 2.0</h3><a
href="./"><img src="./images/index.gif" alt="Index"></a><a href="./"><img
src="./images/home.gif" alt="Home"></a></body></html>
  \ No newline at end of file
  
  
  
  1.1                  httpd-2.0/docs/manual/invoking.xml
  
  Index: invoking.xml
  ===================================================================
  <?xml version='1.0' encoding='UTF-8' ?>
  <!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
  <?xml-stylesheet type="text/xsl" href="./style/manual.en.xsl"?>
  <manualpage>
  <relativepath href="."/>
  
    <title>Starting Apache</title>
  
  <summary>
      <p>On Windows, Apache is normally run as a service on Windows
      NT, or as a console application on Windows 95. For details, see
      <a href="platform/windows.html#run">running Apache for
      Windows</a>.</p>
  
      <p>On Unix, the <a href="programs/httpd.html">httpd</a> program
      is run as a daemon that executes continuously in the
      background to handle requests.  This document describes how
      to invoke <code>httpd</code>.</p>
  </summary>
  
  <section id="startup"><title>How Apache Starts</title>
  
      <p>If the <directive module="mpm_common">Listen</directive>
      specified in the configuration file is default of 80 (or any other
      port below 1024), then it is necessary to have root privileges in
      order to start apache, so that it can bind to this privileged
      port. Once the server has started and performed a few preliminary
      activities such as opening its log files, it will launch several
      <em>child</em> processes which do the work of listening for and
      answering requests from clients. The main <code>httpd</code>
      process continues to run as the root user, but the child processes
      run as a less privileged user. This is controlled by the selected
      <a href="mpm.html">Multi-Processing Module</a>.</p>
  
      <p>The first thing that <code>httpd</code> does when it is
      invoked is to locate and read the <a
      href="configuring.html">configuration file</a>
      <code>httpd.conf</code>. The location of this file is set at
      compile-time, but it is possible to specify its location at run
      time using the <code>-f</code> command-line option as in</p>
  
  <example>/usr/local/apache/bin/httpd -f
        /usr/local/apache/conf/httpd.conf</example>
  
      <p>As an alternative to invoking the <code>httpd</code> binary
      directly, a shell script called <a
      href="programs/apachectl.html">apachectl</a> is provided which
      can be used to control the daemon process with simple commands
      such as <code>apachectl start</code> and <code>apachectl
      stop</code>.</p>
  
      <p>If all goes well during startup, the server will detach from
      the terminal and the command prompt will return almost
      immediately. This indicates that the server is up and running.
      You can then use your browser to connect to the server and view
      the test page in the <directive
      module="core">DocumentRoot</directive> directory
      and the local copy of the documentation linked from that
      page.</p>
  </section>
  
  <section id="errors"><title>Errors During Start-up</title>
  
      <p>If Apache suffers a fatal problem during startup, it will
      write a message describing the problem either to the console or
      to the <directive module="core">ErrorLog</directive> before
      exiting. One of the most common error messages is "<code>Unable
      to bind to Port ...</code>". This message is usually caused by
      either:</p>
  
      <ul>
        <li>Trying to start the server on a privileged port when not
        logged in as the root user; or</li>
  
        <li>Trying to start the server when there is another instance
        of Apache or some other web server already bound to the same
        Port.</li>
      </ul>
  
      <p>For further trouble-shooting instructions, consult the
      Apache <a href="faq/">FAQ</a>.</p>
  </section>
  
  <section id="boot"><title>Starting at Boot-Time</title>
  
      <p>If you want your server to continue running after a system
      reboot, you should add a call to <code>httpd</code> or
      <code>apachectl</code> to your system startup files (typically
      <code>rc.local</code> or a file in an <code>rc.N</code>
      directory). This will start Apache as root. Before doing this
      ensure that your server is properly configured for security and
      access restrictions. The <code>apachectl</code> script is
      designed so that it can often be linked directly as an init
      script, but be sure to check the exact requirements of your
      system.</p>
  </section>
  
  <section id="info"><title>Additional Information</title>
  
      <p>Additional information about the command-line options of <a
      href="programs/httpd.html">httpd</a> and <a
      href="programs/apachectl.html">apachectl</a> as well as other
      support programs included with the server is available on the
      <a href="programs/">Server and Supporting Programs</a> page.
      There is also documentation on all the <a
      href="mod/">modules</a> included with the Apache distribution
      and the <a href="mod/directives.html">directives</a> that they
      provide.</p>
  </section>
  
  </manualpage>
  
  

Mime
View raw message