From 61eca626cdf018b4be59d34099945f94f3a08835 Mon Sep 17 00:00:00 2001 From: Brian Pane Date: Wed, 15 May 2002 00:24:15 +0000 Subject: [PATCH] Added documentation for the new EnableMMAP directive git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95100 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.xml | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml index d57141510f..72a2134934 100644 --- a/docs/manual/mod/core.xml +++ b/docs/manual/mod/core.xml @@ -544,6 +544,45 @@ from the web Location + +EnableMMAP +Controls whether the httpd uses memory-mapping to read files +during delivery +EnableMMAP on|off +EnableMMAP on +server configvirtual host +directory.htaccess + + + +

This directive controls whether the httpd may use memory-mapping + if it needs to read the contents of a file during delivery. By default, + when the handling of a request requires access to the data within a file-- + for example, when delivering a server-parsed file using mod_include-- + Apache memory-maps the file if the OS supports it. +

+

+ This memory-mapping sometimes yields a performance improvement. + But in some environments, it is better to disable the memory-mapping + to prevent operational problems: +

+
    +
  • On some multiprocessor systems, memory-mapping can reduce the + performance of the httpd.
  • +
  • With an NFS-mounted DocumentRoot, + the httpd may crash due tof a segmentation fault if a file is deleted + or truncated while the httpd has it memory-mapped.
  • +
+

+ For server configurations that are vulnerable to these problems, + you should disable memory-mapping of delivered files by specifying: +

+ + EnableMMAP off + +
+
+ ErrorDocument Specifies what the server will return to the client -- 2.50.1