Shorten the comment for EnableMMap, and limit it just to the NFS issue.

The most we could say about preformance is "it's usually better to leave this
on, but sometimes it's better to turn it off", which is not really helpful
to anyone.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95191 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/conf/httpd-std.conf.in b/docs/conf/httpd-std.conf.in
index fccb7c01e9451752fddb47ce82e13f4317b8a683..5a20dee94b8a9fdda1e4583349755f8830d5ef7b 100644 (file)
--- a/docs/conf/httpd-std.conf.in
+++ b/docs/conf/httpd-std.conf.in
@@ -444,15 +444,10 @@ DefaultType text/plain
 HostnameLookups Off
 
 #
-# EnableMMAP: Control whether the httpd may use memory-mapping when
-# delivering files (assuming that the underlying OS supports it).
-# The default is on, which in many cases yields improved performance
-# for mod_include requests.  On some platforms, however, you will
-# get better performance by disabling memory-mapping.  It is also
-# recommended that you disable memory-mapping for directories on
-# NFS-mounted filesystems; otherwise the httpd may crash if you
-# truncate or delete a file while it is being delivered.
-# To disable memory-mapping, use EnableMMAP off.
+# EnableMMAP: Control whether memory-mapping is used to deliver
+# files (assuming that the underlying OS supports it).
+# The default is on; turn this off if you serve from NFS-mounted 
+# filesystems.
 #
 # EnableMMAP off