From owner-freebsd-current Thu Apr 10 18:40:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA18418 for current-outgoing; Thu, 10 Apr 1997 18:40:39 -0700 (PDT) Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA18413 for ; Thu, 10 Apr 1997 18:40:36 -0700 (PDT) Received: from haven.uniserve.com (shell.uniserve.com [198.53.215.121]) by mercury.uniserve.com (8.8.2/8.8.2) with SMTP id SAA24769; Thu, 10 Apr 1997 18:34:06 -0700 (PDT) Date: Thu, 10 Apr 1997 18:44:52 -0700 (PDT) From: Tom Samplonius To: Terry Lambert cc: "Craig W. Shaver" , current@FreeBSD.ORG Subject: Re: NFS/mmap freeze in 2.2R In-Reply-To: <199704110043.RAA10356@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Apr 1997, Terry Lambert wrote: > > > (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. The msync() changes are in INN1.5.1, which has been out for some time. Tom