Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 May 1996 18:40:34 -0700 (PDT)
From:      "Craig Shaver" <craig@ProGroup.COM>
To:        questions@freebsd.org
Subject:   Re: inn & mmap
Message-ID:  <199605140140.SAA00291@seabass.progroup.com>
In-Reply-To: <Pine.NEB.3.92.960511154327.10667J-100000@schizo.cdsnet.net> from "Jaye Mathisen" at May 11, 96 03:44:56 pm

next in thread | previous in thread | raw e-mail | index | archive | help

>From: Jaye Mathisen <mrcpu@cdsnet.net>
>Date: Sat, 11 May 1996 15:44:56 -0700 (PDT)
>
>Hmmm, I thought there was a consensus that something was flaky if the
>active file changed size via newgroup/rmgroup messages with MMAP.
>
>If I turn off all newgroup/rmgroup processing, then I have 0 problems with
>the FreeBSD mmap.  If I process newgroup/rmgroups, I have problems.  Leads
>me to believe something flaky there.
>
>On Thu, 9 May 1996, John S. Dyson wrote:
>
>> > >
>> > >
>> > > >>>>> Cove Schneider <cove@brazil.nbn.com> writes:
>> > > >
>> > > > Has any one run into any problems with inn using mmap under 2.1?
>> > >
>> > > Apparently there is a problem with mmap and inn on 2.1. The workaround
>> > > is - don't use mmap. Fortunately FreeBSD's VM system is very good, so
>> > > it won't cause much of a performance hit if you don't use mmap.
>> > >
>> >
>> > Can you expand on this?  Where did you get the information about mmap
>> > on FreeBSD causing problems with innd?  Is this a problem with the
>> > FreeBSD implementation of mmap or is innd doing something wrong?
>> > i.e., can it be fixed?
>> >
>> > Thanks for the info, I will reconfigure innd and reinstall.
>> >
>> I have been trying to simulate the problem (I have studied the active
>> file mmap code in INND), to no avail.  Additionally, there are
>> other OSes that fully implement mmap that have problems with INND.
>> I really don't know where to look -- if ANYONE can simulate the problem,
>> I would appreciate it.
>>
>> John
>>
>

Here is the information I drug out of the INN faq from the site:

	http://www.math.psu.edu/barr/faq-inn-2

------------------------------

Subject: BSDi 2.0 / FreeBSD / NetBSD

Paul Vixie <paul@vix.com> wrote that for BSDi 2.0the use of mmap for 
use with the history file is ok (add -DMMAP to DBZCFLAGS in config.data), 
but not for active, so set ACT_STYLE to READ. 

For NetBSD1.0 and 1.1 one shouldn't use mmap() unless you add the 
following:

*** icd.c.orig  Wed Jun  7 15:04:05 1995
--- icd.c       Sat Dec 30 16:22:50 1995
***************
*** 369,375 ****
  ICDwriteactive()
  {
  #if   defined(ACT_MMAP)
!     /* No-op. */
  
  #else
  
--- 369,375 ----
  ICDwriteactive()
  {
  #if   defined(ACT_MMAP)
!     msync(ICDactpointer, 0);
  
  #else
 
In NetBSD 1.1 the use of -DMMAP is also ok.(after Curt Sampson <curt@portal.ca>)

FreeBSD users shouldn't use mmap(). There are serious problems and the
performance without is quite good.

------------------------------


-- 
Craig Shaver  (craig@progroup.com) (415)390-0654 
Productivity Group POB 60458 Sunnyvale, CA  94088



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605140140.SAA00291>