From owner-freebsd-questions Thu Dec 7 10:34:21 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA06305 for questions-outgoing; Thu, 7 Dec 1995 10:34:21 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA06285 Thu, 7 Dec 1995 10:34:12 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA05180; Thu, 7 Dec 1995 11:29:02 -0700 From: Terry Lambert Message-Id: <199512071829.LAA05180@phaeton.artisoft.com> Subject: Re: Any operational code using mmap() on FreeBSD ? To: root@buffnet.net (Steve Hovey) Date: Thu, 7 Dec 1995 11:29:02 -0700 (MST) Cc: terry@lambert.org, jau@jau.csc.fi, questions@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: from "Steve Hovey" at Dec 7, 95 09:13:56 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.org Precedence: bulk > > I would (and I'm sure John and other who are actually working on this > > would!) like to see some small test cases with assertions for correct > > results for the test cases you are interested in. Would this be possible? > > 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. The problem with using the 2.05 release for your example is that it is not continuing to be maintained. The question is what are the failure modes on 2.1. If there aren't any, you should upgrade to resolve the problem. If there are, and they are more severe, you should report them to be corrected, since 2.1 *is* being maintained (in the form of the 2.2-current). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.