From: Joshua Slive Date: Sun, 2 Jun 2002 15:48:38 +0000 (+0000) Subject: Update transformations. X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e72f6ea06b6e6466c2b5c2814af597c7ef37b206;p=apache Update transformations. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95470 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en index b3c11ae2cf..845ba1fddd 100644 --- a/docs/manual/mod/mod_proxy.html.en +++ b/docs/manual/mod/mod_proxy.html.en @@ -295,7 +295,7 @@ always served directly, without forwarding to the configured
the subnet 192.168.112.0/21 with a netmask of 21 valid bits (also used in the form 255.255.248.0)
- As a degenerate case, a SubNet with 32 valid bits is the + As a degenerate case, a SubNet with 32 valid bits is the equivalent to an IPAddr, while a SubNet with zero valid bits (e.g., 0.0.0.0/0) is the same as the constant _Default_, matching any IP address. @@ -349,7 +349,7 @@ proxy server:

  Order Deny,Allow
  Deny from all
  Allow from yournetwork.example.com
-<Proxy> +</Proxy>

The following example will process all files in the @@ -359,7 +359,7 @@ server:

<Proxy http://example.com/foo/*>
  SetOutputFilter INCLUDES
-<Proxy> +</Proxy>

ProxyBlock Directive

Description: Words, hosts, or domains that are banned from being proxied
Syntax:ProxyBlock *|word|host|domain diff --git a/docs/manual/mod/perchild.html.en b/docs/manual/mod/perchild.html.en index a09fb4288a..444d4291b5 100644 --- a/docs/manual/mod/perchild.html.en +++ b/docs/manual/mod/perchild.html.en @@ -19,7 +19,8 @@ make it functional.

A single control process launches the number of child processes indicated by the NumServers directive at server startup. Each child process creates threads as specified in the - StartThreads directive. The individual threads then + StartThreads directive. + The individual threads then listen for connections and serve them when they arrive.

Apache always tries to maintain a pool of spare or @@ -28,26 +29,28 @@ make it functional. threads to be created. For each child process, Apache assesses the number of idle threads and creates or destroys threads to keep this number within the boundaries specified by - MinSpareThreads and MaxSpareThreads. + MinSpareThreads + and MaxSpareThreads. Since this process is very self-regulating, it is rarely necessary to modify these directives from their default values. The maximum number of clients that may be served simultaneously is determined by multiplying the number of server processes - that will be created (NumServers) by the maximum + that will be created (NumServers) by the maximum number of threads created in each process - (MaxThreadsPerChild).

+ (MaxThreadsPerChild).

While the parent process is usually started as root under Unix in order to bind to port 80, the child processes and threads are launched by Apache as a less-privileged user. The - User and Group directives are used to + User and Group 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 suexec is used, these directives also set the privileges which will be inherited by CGI scripts.

-

MaxRequestsPerChild controls how frequently the +

MaxRequestsPerChild + controls how frequently the server recycles processes by killing old ones and launching new ones.

diff --git a/docs/manual/mod/prefork.html.en b/docs/manual/mod/prefork.html.en index 882e1fdb4a..ef42c200e7 100644 --- a/docs/manual/mod/prefork.html.en +++ b/docs/manual/mod/prefork.html.en @@ -3,11 +3,22 @@ This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -->prefork- Apache HTTP Server
[APACHE DOCUMENTATION]

Apache HTTP Server Version 2.0

Apache Module prefork

Description:Implements a non-threaded, pre-forking web server
Status:MPM
Module Identifier:mpm_prefork_module

Summary

-

This Multi-Processing Module (MPM) implements a - non-threaded, pre-forking web server which handles request in a - manner very similar to the default behavior of Apache 1.3 on - Unix.

- +

This Multi-Processing Module (MPM) implements a non-threaded, + pre-forking web server that handles requests in a manner similar + to Apache 1.3. It is appropriate for sites that need to avoid + threading for compatibility with non-thread-safe libraries. It + is also the best MPM for isolating each request, so that a problem + with a single request will not affect any other.

+ +

This MPM is very self-regulating, so it is rarely necessary to + adjust its configuration directives. Most important is that + MaxClients be big enough to + handle as many simultaneous requests as you expect to receive, but + small enough to assure that there is enough physical RAM for all + processes.

+ +

Directives

See also

How it Works

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 spare @@ -35,16 +46,12 @@ Apache as a less-privileged user. The User and Group 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 suexec is used, - these directives also set the privileges which will be inherited - by CGI scripts.

+ should have as few privileges beyond that as possible.

MaxRequestsPerChild controls how frequently the server recycles processes by killing old ones and launching new ones.

-

Directives

See also

AcceptMutex Directive

Description: Method that Apache uses to serialize multiple children +

AcceptMutex Directive

Description: Method that Apache uses to serialize multiple children accepting requests on network sockets
Syntax:AcceptMutex default|method
Default:AcceptMutex default
Context:server config
Status:MPM
Module:prefork

The AcceptMutex directives sets the method that Apache uses to serialize multiple children accepting diff --git a/docs/manual/mod/worker.html.en b/docs/manual/mod/worker.html.en index dac5d8964e..8292b36586 100644 --- a/docs/manual/mod/worker.html.en +++ b/docs/manual/mod/worker.html.en @@ -5,45 +5,55 @@ -->worker- Apache HTTP Server

[APACHE DOCUMENTATION]

Apache HTTP Server Version 2.0

Apache Module worker

Description:Multi-Processing Module implementing a hybrid multi-threaded multi-process web server
Status:MPM
Module Identifier:mpm_worker_module

Summary

This Multi-Processing Module (MPM) implements a hybrid - multi-process multi-threaded server. Each process has a fixed + multi-process multi-threaded server. By using threads to serve + requests, it is able to serve a large number of requests with + less system resources than a process-based server. Yet it + retains much of the stability of a process-based server by + keeping multiple processes available, each with many threads.

+ +

The most important directives used to control this MPM are + ThreadsPerChild and + MaxClients. By multiplying + together the value of these directives you define the total number + of simultaneous connections that the server can handle.

+ +

Directives

See also

How it Works

+

Each process has a fixed number of threads. The server adjusts to handle load by increasing or decreasing the number of processes.

A single control process is responsible for launching child - processes. Each child process creates a fixed number of threads - as specified in the ThreadsPerChild directive. The - individual threads then listen for connections and serve them - when they arrive.

+ processes. Each child process creates a fixed number of threads as + specified in the ThreadsPerChild directive. The + individual threads then listen for connections and serve them when + they arrive.

Apache always tries to maintain a pool of spare or idle server threads, which stand ready to serve incoming requests. In this way, clients do not need to wait for a new threads or processes to be created before their requests can be served. Apache assesses the total number of idle threads in all - processes, and forks or kills processes to keep this number - within the boundaries specified by MinSpareThreads - and MaxSpareThreads. Since this process is very - self-regulating, it is rarely necessary to modify these - directives from their default values. The maximum number of + processes, and forks or kills processes to keep this number within + the boundaries specified by MinSpareThreads and MaxSpareThreads. Since this + process is very self-regulating, it is rarely necessary to modify + these directives from their default values. The maximum number of clients that may be served simultaneously is determined by multiplying the maximum number of server processes that will be - created (MaxClients) by the number of threads - created in each process (ThreadsPerChild).

- -

While the parent process is usually started as root under - Unix in order to bind to port 80, the child processes and - threads are launched by Apache as a less-privileged user. The - User and Group 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 suexec is used, these directives also - set the privileges which will be inherited by CGI scripts.

+ created (MaxClients) by + the number of threads created in each process (ThreadsPerChild).

-

MaxRequestsPerChild controls how frequently the - server recycles processes by killing old ones and launching new - ones.

+

While the parent process is usually started as root under Unix + in order to bind to port 80, the child processes and threads are + launched by Apache as a less-privileged user. The User and Group 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 suexec is used, + these directives also set the privileges which will be inherited + by CGI scripts.

-

See also: Setting which addresses and - ports Apache uses.

-

Directives

Apache HTTP Server Version 2.0

IndexHome \ No newline at end of file +

MaxRequestsPerChild + controls how frequently the server recycles processes by killing + old ones and launching new ones.

+

Apache HTTP Server Version 2.0

IndexHome \ No newline at end of file