From owner-freebsd-questions  Thu Dec  7 06:39:58 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA16824
          for questions-outgoing; Thu, 7 Dec 1995 06:39:58 -0800 (PST)
Received: (from dyson@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA16815
          Thu, 7 Dec 1995 06:39:53 -0800 (PST)
From: John Dyson <dyson>
Message-Id: <199512071439.GAA16815@freefall.freebsd.org>
Subject: Re: Any operational code using mmap() on FreeBSD ?
To: root@buffnet.net (Steve Hovey)
Date: Thu, 7 Dec 1995 06:39:53 -0800 (PST)
Cc: terry@lambert.org, jau@jau.csc.fi, questions@freebsd.org,
        hackers@freebsd.org
In-Reply-To: <Pine.SCO.3.91.951207091243.28880D-100000@buffnet1.buffnet.net> from "Steve Hovey" at Dec 7, 95 09:13:56 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-questions@freebsd.org
Precedence: bulk

> 
> MMAP under freebsd 2.05-R is broken.  I run an INN news server on 2.0.5R 
> and if I compiled it using MMAP, the correct values were not maintained 
> in the active file.  This problems occurred when usage got to the size 
> that virtual ram swapping came into play.
> 
Yep, there are some problems -- the code in current is better.  The
problem has to do with  entirely bogus msync code. (That I wrote.)  Also,
don't *even* think about using NFS and mmap for writable regions in
2.0.5. 

John
dyson@freebsd.org