You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Brad Nicholes <BN...@novell.com> on 2002/09/16 20:06:48 UTC

Re: cvs commit: httpd-2.0/docs/conf httpd-nw.conf

    I keep meaning to do this but for some reason I just have never
gotten around to it.  We (NetWare) no longer use httpd-nw.conf and it
should probably be removed.  All of the NetWare specific configurations
have been either folded into httpd-std.conf.in or applied through
build/mkconfNW.awk.  The correct thing to do in this case might be to
wrap the statements with an <IfModule !mpm_netware.c>...</IfModule>.  I
will remove httpd-nw.conf to eliminate having to keep it up to date. 

Brad

Brad Nicholes
Senior Software Engineer
Novell, Inc., the leading provider of Net business solutions
http://www.novell.com 

>>> wrowe@apache.org Monday, September 16, 2002 11:19:35 AM >>>
wrowe       2002/09/16 10:19:35

  Modified:    docs/conf httpd-nw.conf
  Log:
    APR_HAS_MMAP == 0 in apr.hnw, so we can presume that this directive
is
    a noop for today.
  
  Revision  Changes    Path
  1.24      +0 -10     httpd-2.0/docs/conf/httpd-nw.conf
  
  Index: httpd-nw.conf
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/conf/httpd-nw.conf,v
  retrieving revision 1.23
  retrieving revision 1.24
  diff -u -r1.23 -r1.24
  --- httpd-nw.conf	16 Sep 2002 16:57:04 -0000	1.23
  +++ httpd-nw.conf	16 Sep 2002 17:19:35 -0000	1.24
  @@ -353,16 +353,6 @@
   HostnameLookups 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.  On some systems, turning it off (regardless of
  -# filesystem) can improve performance; for details, please see
  -# http://httpd.apache.org/docs-2.0/mod/core.html#enablemmap 
  -#
  -#EnableMMAP off
  -
  -#
   # ErrorLog: The location of the error log file.
   # If you do not specify an ErrorLog directive within a
<VirtualHost>
   # container, error messages relating to that virtual host will be