From owner-freebsd-stable Fri Aug 14 01:02:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16210 for freebsd-stable-outgoing; Fri, 14 Aug 1998 01:02:24 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16205; Fri, 14 Aug 1998 01:02:23 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.7/8.7.3) with SMTP id BAA18050; Fri, 14 Aug 1998 01:01:43 -0700 (PDT) Date: Fri, 14 Aug 1998 01:01:43 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: David Greenman cc: peter@sirius.com, hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: More info: Re: vmopar state in 2.2.7? In-Reply-To: <199808140015.RAA17635@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a tad more info that may shed some light. After much wailing and gnashing of teeth, I realized I had copied my INN 2.1 config files built on a 3.0 box to a 2.2 box, and one of the settings was to mmap() the overview files. mmap() for the active file has always had problems with file truncation under the 2.2.x series, as has been well documented. I'm suspicious that mmap() on an NFS mounted file is the culprit here more than anythingelse. Changing it to not mmap() the overfile seems to have corrected the problem, at least so far. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message