mpm_winnt.xml.de revision f893ba443f124b7ab274b641439cc04f1243f99f
2a0b626c070fea0a68a071a4160ff695eb4731dand<?xml version="1.0"?>
2a0b626c070fea0a68a071a4160ff695eb4731dand<!DOCTYPE modulesynopsis SYSTEM "/style/modulesynopsis.dtd">
2a0b626c070fea0a68a071a4160ff695eb4731dand<?xml-stylesheet type="text/xsl" href="/style/manual.de.xsl"?>
2a0b626c070fea0a68a071a4160ff695eb4731dand<!-- English revision: 1.6 -->
2a0b626c070fea0a68a071a4160ff695eb4731dand
2a0b626c070fea0a68a071a4160ff695eb4731dand<!--
2a0b626c070fea0a68a071a4160ff695eb4731dand Copyright 2003-2004 The Apache Software Foundation
2a0b626c070fea0a68a071a4160ff695eb4731dand
2a0b626c070fea0a68a071a4160ff695eb4731dand Licensed under the Apache License, Version 2.0 (the "License");
2a0b626c070fea0a68a071a4160ff695eb4731dand you may not use this file except in compliance with the License.
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen You may obtain a copy of the License at
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen http://www.apache.org/licenses/LICENSE-2.0
d29d9ab4614ff992b0e8de6e2b88d52b6f1f153erbowen
2a0b626c070fea0a68a071a4160ff695eb4731dand Unless required by applicable law or agreed to in writing, software
2a0b626c070fea0a68a071a4160ff695eb4731dand distributed under the License is distributed on an "AS IS" BASIS,
d229f940abfb2490dee17979e9a5ff31b7012eb5rbowen WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
3f08db06526d6901aa08c110b5bc7dde6bc39905nd See the License for the specific language governing permissions and
2a0b626c070fea0a68a071a4160ff695eb4731dand limitations under the License.
2a0b626c070fea0a68a071a4160ff695eb4731dand-->
2a0b626c070fea0a68a071a4160ff695eb4731dand
3f08db06526d6901aa08c110b5bc7dde6bc39905nd<modulesynopsis metafile="mpm_winnt.xml.meta">
2a0b626c070fea0a68a071a4160ff695eb4731dand
2a0b626c070fea0a68a071a4160ff695eb4731dand<name>mpm_winnt</name>
2a0b626c070fea0a68a071a4160ff695eb4731dand<description> Das Multi-Processing-Modul ist optimiert f&uuml;r
27dcd8d81085fd60aadcd8a9bad35a607b26b758nilgun Windows NT.</description>
2a0b626c070fea0a68a071a4160ff695eb4731dand<status>MPM</status>
e609c337f729875bc20e01096c7e610f45356f54nilgun<sourcefile>mpm_winnt.c</sourcefile>
f086b4b402fa9a2fefc7dda85de2a3cc1cd0a654rjung<identifier>mpm_winnt_module</identifier>
2a0b626c070fea0a68a071a4160ff695eb4731dand
4b575a6b6704b516f22d65a3ad35696d7b9ba372rpluem<summary>
4b575a6b6704b516f22d65a3ad35696d7b9ba372rpluem <p>Dieses Multi-Processing-Modul (MPM) ist die Voreinstellung
4b575a6b6704b516f22d65a3ad35696d7b9ba372rpluem f&uuml;r das Betriebssystem Windows NT. Es verwendet einen einzelnen
4b575a6b6704b516f22d65a3ad35696d7b9ba372rpluem Steuerprozess, der einen einzelnen Kindprozess startet, welcher
2a0b626c070fea0a68a071a4160ff695eb4731dand wiederum Threads zur Bedienung von Anfragen erstellt.</p>
2a0b626c070fea0a68a071a4160ff695eb4731dand</summary>
2a0b626c070fea0a68a071a4160ff695eb4731dand
2a0b626c070fea0a68a071a4160ff695eb4731dand<directivesynopsis location="mpm_common"><name>CoreDumpDirectory</name>
2a0b626c070fea0a68a071a4160ff695eb4731dand</directivesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand<directivesynopsis location="mpm_common"><name>PidFile</name>
2a0b626c070fea0a68a071a4160ff695eb4731dand</directivesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand<directivesynopsis location="mpm_common"><name>Listen</name>
2a0b626c070fea0a68a071a4160ff695eb4731dand</directivesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand<directivesynopsis location="mpm_common"><name>ListenBacklog</name>
2a0b626c070fea0a68a071a4160ff695eb4731dand</directivesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand<directivesynopsis location="mpm_common"><name>MaxRequestsPerChild</name>
2a0b626c070fea0a68a071a4160ff695eb4731dand</directivesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand<directivesynopsis location="mpm_common"><name>ScoreBoardFile</name>
2a0b626c070fea0a68a071a4160ff695eb4731dand</directivesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand<directivesynopsis location="mpm_common"><name>SendBufferSize</name>
30471a4650391f57975f60bbb6e4a90be7b284bfhumbedooh</directivesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand<directivesynopsis location="mpm_common"><name>ThreadLimit</name>
2a0b626c070fea0a68a071a4160ff695eb4731dand</directivesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand<directivesynopsis location="mpm_common"><name>ThreadsPerChild</name>
2a0b626c070fea0a68a071a4160ff695eb4731dand</directivesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand
2a0b626c070fea0a68a071a4160ff695eb4731dand<directivesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand<name>Win32DisableAcceptEx</name>
2a0b626c070fea0a68a071a4160ff695eb4731dand<description>F&uuml;r die Annahme von Netzwerkverbindungen wird accept() anstelle von AcceptEx() verwendet</description>
2a0b626c070fea0a68a071a4160ff695eb4731dand<syntax>Win32DisableAcceptEx</syntax>
2a0b626c070fea0a68a071a4160ff695eb4731dand<default>AcceptEx() ist standardm&auml;&szlig;ig aktiviert. Verwenden Sie diese
2a0b626c070fea0a68a071a4160ff695eb4731dandDirektive, um den Gebrauch von AcceptEx() zu deaktivieren.</default>
2a0b626c070fea0a68a071a4160ff695eb4731dand<contextlist><context>server config</context></contextlist>
2a0b626c070fea0a68a071a4160ff695eb4731dand<compatibility>Verf&uuml;gbar ab Version 2.0.49</compatibility>
2a0b626c070fea0a68a071a4160ff695eb4731dand
2a0b626c070fea0a68a071a4160ff695eb4731dand<usage>
2a0b626c070fea0a68a071a4160ff695eb4731dand <p><code>AcceptEx()</code> ist eine Schnittstelle zu Microsoft Winsock v2,
2a0b626c070fea0a68a071a4160ff695eb4731dand die unter bestimmten Umst&auml;nden einige Leistungsverbesserungen
2a0b626c070fea0a68a071a4160ff695eb4731dand gegen&uuml;ber der <code>accept()</code>-API von BSD bietet. Einige beliebte
2a0b626c070fea0a68a071a4160ff695eb4731dand Windows-Produkte, typischerweise Virenscanner oder VPN-Pakete, besitzen
2a0b626c070fea0a68a071a4160ff695eb4731dand jedoch Fehler, welche den einwandfreien Betrieb von <code>AcceptEx()</code>
2a0b626c070fea0a68a071a4160ff695eb4731dand st&ouml;ren. Wenn Sie einen Fehler wie:</p>
2a0b626c070fea0a68a071a4160ff695eb4731dand
2a0b626c070fea0a68a071a4160ff695eb4731dand <example>
2a0b626c070fea0a68a071a4160ff695eb4731dand [error] (730038)An operation was attempted on something that is
2a0b626c070fea0a68a071a4160ff695eb4731dand not a socket.: winnt_accept: AcceptEx failed. Attempting to recover.
2a0b626c070fea0a68a071a4160ff695eb4731dand </example>
2a0b626c070fea0a68a071a4160ff695eb4731dand
2a0b626c070fea0a68a071a4160ff695eb4731dand <p>erhalten, sollten Sie diese Direktive verwenden, um den Gebrauch von
2a0b626c070fea0a68a071a4160ff695eb4731dand <code>AcceptEx()</code> zu unterbinden.</p>
2a0b626c070fea0a68a071a4160ff695eb4731dand</usage>
2a0b626c070fea0a68a071a4160ff695eb4731dand</directivesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand
2a0b626c070fea0a68a071a4160ff695eb4731dand</modulesynopsis>
2a0b626c070fea0a68a071a4160ff695eb4731dand