From: Joshua Slive Date: Sun, 19 Nov 2000 05:02:36 +0000 (+0000) Subject: Woops, I just discovere UNIX_DAEMON_COMMANDS and LISTEN_COMMANDS. Add X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0d8d3135f4b17ca919b3c5875f1c13731bfeda6d;p=apache Woops, I just discovere UNIX_DAEMON_COMMANDS and LISTEN_COMMANDS. Add in those directives and dexter. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@87021 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/dexter.html b/docs/manual/mod/dexter.html new file mode 100644 index 0000000000..b214947e85 --- /dev/null +++ b/docs/manual/mod/dexter.html @@ -0,0 +1,147 @@ + + + +Apache MPM mpmt_pthread + + + + + + +

Multi-Processing Module mpmt_pthread

+This Multi-Processing Module controls process and thread creation +using the pthread interface. +

+ +

Status: MPM +
+Source File: mpmt_pthread.c +
+Module Identifier: mpm_mpmt_pthread_module +

+ +

Summary

+ +

This Multi-Processing Module (MPM) is the default for most +unix-like operating systems. It uses pthread system calls to create a +hybrid multi-process multi-threaded server. The server starts a fixed +number of processes. The server adjusts to handle load by increasing +or decreasing the number of threads.

+ + +

Directives

+ + +

ConnectionStatus directive

Syntax: +Default: +Context: server config
+Status: MPM

+Module: dexter

+ +

Whether or not to maintain status information on current +connections

+ +

NumServers directive

Syntax: +Default: +Context: server config
+Status: MPM

+Module: dexter

+ +

Number of children alive at the same time.

+ +

StartThreads directive

Syntax: +Default: +Context: server config
+Status: MPM

+Module: dexter

+ +

Number of threads each child creates.

+ + + + diff --git a/docs/manual/mod/index.html b/docs/manual/mod/index.html index 81f79d7d75..6f7785d7af 100644 --- a/docs/manual/mod/index.html +++ b/docs/manual/mod/index.html @@ -29,9 +29,14 @@ directives.

Core: Core Apache features. +
dexter +: Multi-Processing Model with Threading via Pthreads; Fixed number +of processes, variable number of threads/child
mpmt_pthread: Multi-Processing Model with Threading via Pthreads; Variable number of processes, constant number of threads/child +
prefork +: Non-threaded preforking processes model similar to Apache 1.3.

Other Modules

diff --git a/docs/manual/mod/mpm_common.html b/docs/manual/mod/mpm_common.html index 75dd0b8082..7201cd2735 100644 --- a/docs/manual/mod/mpm_common.html +++ b/docs/manual/mod/mpm_common.html @@ -23,15 +23,20 @@ than one multi-processing module (MPM).

@@ -65,6 +70,57 @@ this should not be writable by the user the server runs as, core dumps won't normally get written. If you want a core dump for debugging, you can use this directive to place it in a different location.

+ +

Group directive

+ +Syntax: Group unix-group
+Default: Group #-1
+Context: server config, virtual host
+Status: MPM
+Module: mpmt_pthread, prefork

+ +The Group directive sets the group under which the server will answer requests. +In order to use this directive, the stand-alone server must be run initially +as root. Unix-group is one of: +

A group name +: Refers to the given group by name. +
# followed by a group number. +: Refers to a group by its number. +

+ +It is recommended that you set up a new group specifically for running the +server. Some admins use user nobody, but this is not always +possible or desirable.

+ +Note: if you start the server as a non-root user, it will fail to change +to the specified group, and will instead continue to run as the group of the +original user.

+ +Special note: Use of this directive in <VirtualHost> requires a +properly configured suEXEC wrapper. +When used inside a <VirtualHost> in this manner, only the group +that CGIs are run as is affected. Non-CGI requests are still processed +as the group specified in the main Group directive.

+ +SECURITY: See User for a discussion of the security +considerations.

PidFile directive

The PidFile is subject to the same warnings about log file placement and security.

Listen directive

Syntax: +Listen [IP address:]port number
+Context: server config
+Status: MPM
+Module: mpmt_pthread, prefork

+ + +

The Listen directive instructs Apache to listen to more than one IP +address or port; by default it responds to requests on all IP +interfaces, but only on the port given by the Port directive.

+ +Listen can be used instead of BindAddress and Port. It tells +the server to accept incoming requests on the specified port or +address-and-port combination. If the first format is used, with a port +number only, the server listens to the given port on all interfaces, +instead of the port given by the Port directive. If an IP +address is given as well as a port, the server will listen on the +given port and interface.

+ +Note that you may still require a Port directive so +that URLs that Apache generates that point to your server still +work.

+ +Multiple Listen directives may be used +to specify a number of addresses and ports to listen to. The server +will respond to requests from any of the listed addresses and +ports. +

+ +For example, to make the server accept connections on both port +80 and port 8000, use: +

+   Listen 80
+   Listen 8000
+

+ +To make the server accept connections on two specified +interfaces and port numbers, use +

+   Listen 192.170.2.1:80
+   Listen 192.170.2.5:8000
+

+ +

See Also: +DNS Issues
+See Also: +Setting which addresses and ports Apache uses
+See Also: +Known Bugs +

+ +

ListenBacklog directive

Syntax: ListenBacklog backlog
+Default: ListenBacklog 511
+Context: server config
+Status: MPM
+Module: mpmt_pthread, prefork

+ +

The maximum length of the queue of pending connections. Generally no +tuning is needed or desired, however on some systems it is desirable +to increase this when under a TCP SYN flood attack. See +the backlog parameter to the listen(2) system call. +

This will often be limited to a smaller number by the operating +system. This varies from OS to OS. Also note that many OSes do not +use exactly what is specified as the backlog, but use a number based on +(but normally larger than) what is set. +

LockFile directive

Stopping and Restarting Apache

+ +

SendBufferSize directive

+ +

Syntax: SendBufferSize bytes
+Context: server config
+Status: MPM
+Module: mpmt_pthread, prefork

+ +The server will set the TCP buffer size to the number of bytes +specified. Very useful to increase past standard OS defaults on high +speed high latency (i.e., 100ms or so, such as transcontinental +fast pipes) +

StartServers directive

@@ -394,7 +574,7 @@ on the load, there is usually little reason to adjust this parameter.

Status: Base
+>Status: MPM

This directive sets the number of threads created by each child process.

+ + +

User directive

+ +

Syntax: User unix-userid
+Default: User #-1
+Context: server config, virtual host
+Status: core
+Compatibility: Removed in version 2.0.

+Module: mpmt_pthread, prefork

+ +The User directive sets the userid as which the server will answer requests. +In order to use this directive, the standalone server must be run initially +as root. Unix-userid is one of: +

A username +: Refers to the given user by name. +
# followed by a user number. +: Refers to a user by their number. +

+ +The user should have no privileges which result in it being able to access +files which are not intended to be visible to the outside world, and +similarly, the user should not be able to execute code which is not +meant for httpd requests. It is recommended that you set up a new user and +group specifically for running the server. Some admins use user +nobody, but this is not always possible or desirable. +For example mod_proxy's cache, when enabled, must be accessible to this user +(see the CacheRoot +directive).

+ +Notes: If you start the server as a non-root user, it will fail to change +to the lesser privileged user, and will instead continue to run as +that original user. If you do start the server as root, then it is normal +for the parent process to remain running as root.

+ +Special note: Use of this directive in <VirtualHost> requires a +properly configured suEXEC wrapper. +When used inside a <VirtualHost> in this manner, only the user +that CGIs are run as is affected. Non-CGI requests are still processed +with the user specified in the main User directive.

+ +SECURITY: Don't set User (or Group) to +root unless you know exactly what you are doing, and what the +dangers are.

diff --git a/docs/manual/mod/mpmt_pthread.html b/docs/manual/mod/mpmt_pthread.html index a4ab2c5710..5436378ceb 100644 --- a/docs/manual/mod/mpmt_pthread.html +++ b/docs/manual/mod/mpmt_pthread.html @@ -48,15 +48,20 @@ decreasing the number of processes.

Directives

diff --git a/docs/manual/mod/prefork.html b/docs/manual/mod/prefork.html index ba305704f1..9425cf9ee1 100644 --- a/docs/manual/mod/prefork.html +++ b/docs/manual/mod/prefork.html @@ -45,17 +45,22 @@ very similar to the default behavior of Apache 1.3 on Unix.