Update the "bind" docs, remove the stuff from "server-wide.html" that

will now go in the MPMs, and update prefork.html with that documentation.


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

1 files changed, 0 insertions, 104 deletions

diff --git a/docs/manual/server-wide.html.en b/docs/manual/server-wide.html.en
index be987a8f5a..bf8fa72a3f 100644
--- a/docs/manual/server-wide.html.en
+++ b/docs/manual/server-wide.html.en
@@ -22,8 +22,6 @@ the basic operations of the server.</p>
 <ul>
 <li><a href="#identification">Server Identification</a></li>
 <li><a href="#locations">File Locations</a></li>
-<li><a href="#process">Process Creation</a></li>
-<li><a href="#network">Network Configuration</a></li>
 <li><a href="#resource">Limiting Resource Usage</a></li>
 </ul>
 
@@ -82,108 +80,6 @@ href="misc/security_tips.html">security tips</a> documentation for
 more details.</p>
 
 <hr>
-
-<h2><a name="process">Process Creation</a></h2>
-
-<table border="1">
-<tr><td valign="top">
-<strong>Related Directives</strong><br><br>
-
-<a href="mod/core.html#bs2000account">BS2000Account</a><br>
-<a href="mod/core.html#group">Group</a><br>
-<a href="mod/core.html#maxclients">MaxClients</a><br>
-<a href="mod/core.html#maxrequestsperchild">MaxRequestsPerChild</a><br>
-<a href="mod/core.html#maxspareservers">MaxSpareServers</a><br>
-<a href="mod/core.html#minspareservers">MinSpareServers</a><br>
-<a href="mod/core.html#servertype">ServerType</a><br>
-<a href="mod/core.html#startservers">StartServers</a><br>
-<a href="mod/core.html#threadsperchild">ThreadsPerChild</a><br>
-<a href="mod/core.html#user">User</a><br>
-</td></tr></table>
-
-<p>When <code>ServerType</code> is set to its recommended value of
-<code>Standalone</code>, Apache 1.3 for Unix is a pre-forking web
-server.  A single control process is responsible for launching child
-processes which listen for connections and serve them when they
-arrive.  Apache always tries to maintain several <em>spare</em> or
-idle server processes, which stand ready to serve incoming requests.
-In this way, clients do not need to wait for a new child processes to
-be forked before their requests can be served.</p>
-
-<p>The <code>StartServers</code>, <code>MinSpareServers</code>,
-<code>MaxSpareServers</code>, and <code>MaxServers</code> regulate how
-the parent process creates children to serve requests.  In general,
-Apache is very self-regulating, so most sites do not need to adjust
-these directives from their default values.  Sites which need to serve
-more than 256 simultaneous requests may need to increase
-<code>MaxClients</code>, while sites with limited memory may need to
-decrease <code>MaxClients</code> to keep the server from thrashing
-(swapping memory to disk and back).  More information about tuning
-process creation is provided in the <a
-href="misc/perf-tuning.html">performance hints</a> documentation.</p>
-
-<p>While the parent process is usually started as root under Unix
-in order to bind to port 80, the child processes are launched
-by Apache as a less-privileged user.  The <code>User</code> and
-<code>Group</code> directives are used to set the privileges
-of the Apache child processes.  The child processes must
-be able to read all the content that will be served, but
-should have as few privileges beyond that as possible.
-In addition, unless <a href="suexec.html">suexec</a> is used,
-these directives also set the privileges which will be inherited
-by CGI scripts.</p>
-
-<p><code>MaxRequestsPerChild</code> controls how frequently the server
-recycles processes by killing old ones and launching new ones.</p>
-
-<p>Under Windows, Apache launches one control process and one
-child process.  The child process creates multiple threads to
-serve requests.  The number of threads is controlled by the
-<code>ThreadsPerChild</code> directive.</p>
-
-<hr>
-
-<h2><a name="network">Network Configuration</a></h2>
-
-<table border="1">
-<tr><td valign="top">
-<strong>Related Directives</strong><br><br>
-
-<a href="mod/core.html#bindaddress">BindAddress</a><br>
-<a href="mod/core.html#keepalive">KeepAlive</a><br>
-<a href="mod/core.html#keepalivetimeout">KeepAliveTimeout</a><br>
-<a href="mod/core.html#listen">Listen</a><br>
-<a href="mod/core.html#listenbacklog">ListenBackLog</a><br>
-<a href="mod/core.html#maxkeepaliverequests">MaxKeepAliveRequests</a><br>
-<a href="mod/core.html#port">Port</a><br>
-<a href="mod/core.html#sendbuffersize">SendBufferSize</a><br>
-<a href="mod/core.html#timeOut">TimeOut</a><br>
-</td></tr></table>
-
-<p>When Apache starts, it connects to some port and address on the
-local machine and waits for incoming requests. By default, it listens
-to all addresses on the machine, and to the port as specified by the
-<code>Port</code> directive in the server configuration.  However, it
-can be told to listen to more than one port, to listen to only
-selected addresses, or a combination. This is often combined with the
-<a href="vhosts/">Virtual Host</a> feature which determines how Apache
-responds to different IP addresses, hostnames and ports.</p>
-
-<p>There are two directives used to restrict or specify which addresses
-and ports Apache listens to.  The <code>BindAddress</code> directive
-is used to restrict the server to listening to a single IP address.
-The <code>Listen</code> directive can be used to specify multiple
-IP addresses and/or Ports to which Apache will listen.</p>
-
-<p>The <code>ListenBackLog</code>, <code>SendBufferSize</code>, and
-<code>TimeOut</code> directives are used to adjust how Apache
-interacts with the network.</p>
-
-<p>The <code>KeepAlive</code>, <code>KeepAliveTimeout</code>, 
-and <code>MaxKeepAliveRequests</code> directives are used to
-configure how Apache handles persistent connections.</p>
-
-<hr>
 <h2><a name="resource">Limiting Resource Usage</a></h2>
 <table border="1">
 <tr><td valign="top">