Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.arcetri.astro.it/manual/en/mod/mpm_winnt.html
Дата изменения: Fri Nov 20 00:43:56 2015
Дата индексирования: Sun Apr 10 06:18:35 2016
Кодировка:

Поисковые слова: р п п р п р п п р п р п п р п р п п р п р п п р п р п п р п c 1999 s4 linear
mpm_winnt - Apache HTTP Server
<-
Apache > HTTP Server > Documentation > Version 2.4 > Modules

Apache MPM winnt

Available Languages:  de  |  en  |  fr  |  ja 

Description:Multi-Processing Module optimized for Windows NT.
Status:MPM
Module Identifier:mpm_winnt_module
Source File:mpm_winnt.c

Summary

This Multi-Processing Module (MPM) is the default for the Windows NT operating systems. It uses a single control process which launches a single child process which in turn creates threads to handle requests

Capacity is configured using the ThreadsPerChild directive, which sets the maximum number of concurrent client connections.

By default, this MPM uses advanced Windows APIs for accepting new client connections. In some configurations, third-party products may interfere with this implementation, with the following messages written to the web server log:

Child: Encountered too many AcceptEx faults accepting client connections.
winnt_mpm: falling back to 'AcceptFilter none'.

The MPM falls back to a safer implementation, but some client requests were not processed correctly. In order to avoid this error, use AcceptFilter with accept filter none.

AcceptFilter none

In Apache httpd 2.0 and 2.2, Win32DisableAcceptEx was used for this purpose.

The WinNT MPM differs from the Unix MPMs such as worker and event in several areas:

Directives

See also

Available Languages:  de  |  en  |  fr  |  ja 

top

Comments

Notice:
This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our mailing lists.