- publishing free software manuals
The Apache HTTP Server Reference Manual
by Apache Software Foundation
Paperback (6"x9"), 862 pages
ISBN 9781906966034
RRP £19.95 ($29.95)

Get a printed copy>>>

3.79  Apache Module beos



Description:

This Multi-Processing Module is optimized for BeOS.

Status:

MPM

Module Identifier:

mpm_beos_module

Source File:

beos.c



Summary

This Multi-Processing Module (MPM) is the default for BeOS. It uses a single control process which creates threads to handle requests.

Directives:

CoreDumpDirectory (p. 1000)

Group (p. 1002)

Listen (p. 1003)

ListenBacklog (p. 1006)

MaxClients (p. 1007)

MaxMemFree (p. 1007)

MaxRequestsPerThread

MaxSpareThreads (p. 1009)

MinSpareThreads (p. 1010)

PidFile (p. 1010)

ReceiveBufferSize (p. 1011)

ScoreBoardFile (p. 1012)

SendBufferSize (p. 1013)

StartThreads (p. 1014)

User (p. 1017)

See also:

  • Setting which addresses and ports Apache uses (p. 1455)

MaxRequestsPerThread Directive

Description:

Limit on the number of requests that an individual thread will handle during its life

Syntax:

MaxRequestsPerThread number

Default:

MaxRequestsPerThread 0

Context:

server config

Status:

MPM

Module:

beos

The MaxRequestsPerThread directive sets the limit on the number of requests that an individual server thread will handle. After MaxRequestsPerThread requests, the thread will die. If MaxRequestsPerThread is 0, then the thread will never expire.

Setting MaxRequestsPerThread to a non-zero limit has two beneficial effects:

  • it limits the amount of memory that a thread can consume by (accidental) memory leakage;
  • by giving threads a finite lifetime, it helps reduce the number of threads when the server load reduces.

Note: For KeepAlive requests, only the first request is counted towards this limit. In effect, it changes the behavior to limit the number of connections per thread.

ISBN 9781906966034The Apache HTTP Server Reference ManualSee the print edition