From a83284e10365f9baf39331e545dde65ecdc99ef1 Mon Sep 17 00:00:00 2001 From: Stefan Fritsch Date: Sat, 1 Oct 2011 20:57:36 +0000 Subject: update xforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1178089 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mpm_common.html.en | 56 +++++++++++++++++++------------------- 1 file changed, 28 insertions(+), 28 deletions(-) (limited to 'docs/manual/mod/mpm_common.html.en') diff --git a/docs/manual/mod/mpm_common.html.en b/docs/manual/mod/mpm_common.html.en index 8fbc40433b..907d31c72c 100644 --- a/docs/manual/mod/mpm_common.html.en +++ b/docs/manual/mod/mpm_common.html.en @@ -68,16 +68,16 @@ switch before dumping core

This controls the directory to which Apache httpd attempts to switch before dumping core. If your operating system is configured to - create core files in the working directory of the crashing process, + create core files in the working directory of the crashing process, CoreDumpDirectory is necessary to change working - directory from the default ServerRoot + directory from the default ServerRoot directory, which should not be writable by the user the server runs as.

-

If you want a core dump for debugging, you can use this directive to +

If you want a core dump for debugging, you can use this directive to place it in a different location. This directive has no effect if your operating system is not configured to write core files to the working directory of the crashing processes.

- +

Core Dumps on Linux

If Apache httpd starts as root and switches to another user, the Linux kernel disables core dumps even if the directory is @@ -93,8 +93,8 @@ switch before dumping core

Specific signals

-

CoreDumpDirectory processing only occurs for - a select set of fatal signals: SIGFPE, SIGILL, SIGABORT, +

CoreDumpDirectory processing only occurs for + a select set of fatal signals: SIGFPE, SIGILL, SIGABORT, SIGSEGV, and SIGBUS.

On some operating systems, SIGQUIT also results in a core dump but does not go through CoreDumpDirectory or @@ -120,7 +120,7 @@ after a crash configured with the --enable-exception-hook option. It enables a hook that allows external modules to plug in and do something after a child crashed.

- +

There are already two modules, mod_whatkilledus and mod_backtrace that make use of this hook. Please have a look at Jeff Trawick's EnableExceptionHook site for more information about these.

@@ -139,7 +139,7 @@ will exit. Compatibility:Available in version 2.2 and later

The GracefulShutdownTimeout specifies - how many seconds after receiving a "graceful-stop" signal, a + how many seconds after receiving a "graceful-stop" signal, a server should continue to run, handling the existing connections.

Setting this value to zero means that the server will wait @@ -199,14 +199,14 @@ The protocol argument was added in 2.1.5 Listen [2001:db8::a00:20ff:fea7:ccea]:80

-

The optional protocol argument is not required for most - configurations. If not specified, https is the default for - port 443 and http the default for all other ports. The +

The optional protocol argument is not required for most + configurations. If not specified, https is the default for + port 443 and http the default for all other ports. The protocol is used to determine which module should handle a request, and - to apply protocol specific optimizations with the + to apply protocol specific optimizations with the AcceptFilter directive.

-

You only need to set the protocol if you are running on non-standard +

You only need to set the protocol if you are running on non-standard ports. For example, running an https site on port 8443:

@@ -345,7 +345,7 @@ simultaneously

Maximum number of idle threads. Different MPMs deal with this directive differently.

-

For worker, the default is +

For worker, the default is MaxSpareThreads 250. This MPM deals with idle threads on a server-wide basis. If there are too many idle threads in the server then child processes are killed until the number of idle @@ -517,7 +517,7 @@ Apache HTTP Server

Sets the server's TCP send buffer size to the number of bytes specified. It is often useful to set this past the OS's standard - default value on high speed, high latency conections + default value on high speed, high latency conections (i.e., 100ms or so, such as transcontinental fast pipes).

If set to the value of 0, the server will use the @@ -603,7 +603,7 @@ Apache HTTP Server there is usually little reason to adjust this parameter.

The default value differs from MPM to MPM. worker - defaults to StartServers 3; prefork + defaults to StartServers 3; prefork defaults to 5; mpmt_os2 defaults to 2.

@@ -702,7 +702,7 @@ and later
top

ThreadStackSize Directive

- @@ -711,11 +711,11 @@ client connections
Description:The size in bytes of the stack used by threads handling +
Description:The size in bytes of the stack used by threads handling client connections
Syntax:ThreadStackSize size
Default:65536 on NetWare; varies on other operating systems
Module:event, mpm_netware, mpmt_os2, mpm_winnt, worker, event
Compatibility:Available in Apache HTTP Server 2.1 and later
-

The ThreadStackSize directive sets the +

The ThreadStackSize directive sets the size of the stack (for autodata) of threads which handle client - connections and call modules to help process those connections. - In most cases the operating system default for stack size is - reasonable, but there are some conditions where it may need to be + connections and call modules to help process those connections. + In most cases the operating system default for stack size is + reasonable, but there are some conditions where it may need to be adjusted:

    @@ -724,13 +724,13 @@ client connections which use a relatively large amount of autodata storage. Those same modules may have worked fine on other platforms where the default thread stack size is larger. This type of crash is - resolved by setting ThreadStackSize to a - value higher than the operating system default. This type of - adjustment is necessary only if the provider of the third-party + resolved by setting ThreadStackSize to a + value higher than the operating system default. This type of + adjustment is necessary only if the provider of the third-party module specifies that it is required, or if diagnosis of an Apache httpd crash indicates that the thread stack size was too small. -
  • On platforms where the default thread stack size is +
  • On platforms where the default thread stack size is significantly larger than necessary for the web server configuration, a higher number of threads per child process will be achievable if ThreadStackSize is @@ -743,9 +743,9 @@ client connections the current ThreadStackSize setting.
  • On Linux, this directive can only be used to increase the default - stack size, as the underlying system call uses the value as a - minimum stack size. The (often large) soft limit for - ulimit -s (8MB if unlimited) is used as the default stack + stack size, as the underlying system call uses the value as a + minimum stack size. The (often large) soft limit for + ulimit -s (8MB if unlimited) is used as the default stack size.
-- cgit v1.2.3