From owner-freebsd-current  Thu Apr 10 19:01:47 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA19385
          for current-outgoing; Thu, 10 Apr 1997 19:01:47 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA19380
          for <current@freebsd.org>; Thu, 10 Apr 1997 19:01:41 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.8.4/8.6.9) id VAA01503; Thu, 10 Apr 1997 21:00:31 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199704110200.VAA01503@dyson.iquest.net>
Subject: Re: NFS/mmap freeze in 2.2R
In-Reply-To: <199704110043.RAA10356@phaeton.artisoft.com> from Terry Lambert at "Apr 10, 97 05:43:25 pm"
To: terry@lambert.org (Terry Lambert)
Date: Thu, 10 Apr 1997 21:00:31 -0500 (EST)
Cc: craig@tuna.progroup.com, terry@lambert.org, current@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> PS: If the problem *is* cured by the msync() patch, I think the only VM
> problem is in the way the error is reported as a FreeBSD error instead
> of an application error, and John may do well to fix *that*, rather
> than to compromise the mmap() behaviour for the benefit INN...
> 
Uhhh...  You mean my new sysctl vm.modify.mmap.behavior.for.inn isn't
a good idea?

Geesh :-).

John