From owner-freebsd-current Thu Apr 10 18:03:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA15758 for current-outgoing; Thu, 10 Apr 1997 18:03:05 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA15745 for ; Thu, 10 Apr 1997 18:02:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA10356; Thu, 10 Apr 1997 17:43:25 -0700 From: Terry Lambert Message-Id: <199704110043.RAA10356@phaeton.artisoft.com> Subject: Re: NFS/mmap freeze in 2.2R To: craig@tuna.progroup.com (Craig W. Shaver) Date: Thu, 10 Apr 1997 17:43:25 -0700 (MST) Cc: terry@lambert.org, current@freebsd.org In-Reply-To: <199704102346.QAA04627@tuna.ProGroup.COM> from "Craig W. Shaver" at Apr 10, 97 04:46:19 pm X-Mailer: ELM [version 2.4 PL24] 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 > > (If you are running the msync() patch, then never mind). > > Terry, where can I find the INN msync() patch, and what version of INN > is it to be applied against? Ugh. That's a nice hard question. I typically don't run INN. Your best bet would be to check the -current list archives for the keywords "INN" and "msync". Barring that, if you could wait, you should be able to take John Dyson up on his offer to fix the VM problem. 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... Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.