summaryrefslogtreecommitdiff
path: root/docs/manual/mod/beos.xml.de
blob: 1a4c5149028002cb53cb42ee387d052763ce768b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
<?xml version="1.0"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.de.xsl"?>
<!-- English Revision: 421174 -->

<!--
 Licensed to the Apache Software Foundation (ASF) under one or more
 contributor license agreements.  See the NOTICE file distributed with
 this work for additional information regarding copyright ownership.
 The ASF licenses this file to You under the Apache License, Version 2.0
 (the "License"); you may not use this file except in compliance with
 the License.  You may obtain a copy of the License at

     http://www.apache.org/licenses/LICENSE-2.0

 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
-->

<modulesynopsis metafile="beos.xml.meta">
<name>beos</name>
<description>Dieses Multi-Processing-Modul ist f&uuml;r BeOS
  optimiert.</description>
<status>MPM</status>
<sourcefile>beos.c</sourcefile>
<identifier>mpm_beos_module</identifier>

<summary>
   <p>Dieses Multi-Processing-Modul (MPM) ist das Standardmodul f&uuml;r BeOS.
     Es benutzt einen einzelnen Steuerprozess welcher Threads f&uuml;r die
     Bedienung der Anfragen erzeugt.</p>
</summary>
<seealso><a href="../bind.html">Adress- und Port-Einstellungen</a>
</seealso>

<directivesynopsis location="mpm_common"><name>User</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>Group</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>Listen</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>ListenBacklog</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>ReceiveBufferSize</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>SendBufferSize</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>StartThreads</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>MinSpareThreads</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>MaxSpareThreads</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>MaxClients</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>CoreDumpDirectory</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>MaxMemFree</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>PidFile</name>
</directivesynopsis>
<directivesynopsis location="mpm_common"><name>ScoreBoardFile</name>
</directivesynopsis>

<directivesynopsis>
<name>MaxRequestsPerThread</name>
<description>Die maximale Anzahl von Anfragen, die ein einzelner Thread
  w&auml;hrend seiner Lebensdauer bedient.</description>
<syntax>MaxRequestsPerThread <var>Anzahl</var></syntax>
<default>MaxRequestsPerThread 0</default>
<contextlist><context>server config</context></contextlist>

<usage>
  <p>Die Direktive <directive>MaxRequestsPerThread</directive> legt die 
    Anzahl der Anfragen fest, die ein einzelner Server-Thread bedient. Nach 
    Erreichen der angegebenen Anzahl von Anfragen wird der Thread beendet. 
    Wird f&uuml;r <directive>MaxRequestsPerThread</directive> der Wert 
    <code>0</code> angegeben, wird der Thread niemals beendet.</p>

    <p>Das Setzen von <directive>MaxRequestsPerThread</directive> auf einen
    Wert ungleich null hat zwei Vorteile:</p>

    <ul>
      <li>Die Menge des von einem Thread ben&ouml;tigten Speicherplatzes
       bei (unvorhergesehenen) Speicherproblemen kann begrenzt werden;</li>

      <li>Threads mit begrenzter Lebensdauer reduzieren die Anzahl 
      der Threads bei reduzierter Serverlast.</li>
    </ul>

    <note><title>Hinweis:</title>
      <p>Bei <directive module="core">KeepAlive</directive>-Anfragen wird nur die
      erste Anfrage auf das Maximum angerechnet. Das f&uuml;hrt dazu, dass
      die Anzahl der <em>Verbindungen</em>
      pro Thread reduziert wird.</p>
    </note>
</usage>
</directivesynopsis>

</modulesynopsis>