Date: Thu, 10 Apr 1997 18:44:52 -0700 (PDT) From: Tom Samplonius <tom@uniserve.com> To: Terry Lambert <terry@lambert.org> Cc: "Craig W. Shaver" <craig@tuna.progroup.com>, current@FreeBSD.ORG Subject: Re: NFS/mmap freeze in 2.2R Message-ID: <Pine.NEB.3.95.970410184402.10319A-100000@haven.uniserve.com> In-Reply-To: <199704110043.RAA10356@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.970410184402.10319A-100000>