From owner-freebsd-current Mon Jul 27 08:02:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00603 for freebsd-current-outgoing; Mon, 27 Jul 1998 08:02:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00460 for ; Mon, 27 Jul 1998 08:01:56 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id IAA28873; Mon, 27 Jul 1998 08:01:13 -0700 (PDT) Message-Id: <199807271501.IAA28873@mailgate.cadence.com> Received: from unknown(194.32.96.136) by mailgate.cadence.com via smap (mjr-v1.2) id xma901551672.028868; Mon, 27 Jul 98 08:01:12 -0700 Comments: Authenticated sender is From: "Duncan Barclay" To: Karl Denninger , current@FreeBSD.ORG, Pierre Beyssac Date: Mon, 27 Jul 1998 16:00:55 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: MMAP problems Reply-to: dmlb@ragnet.demon.co.uk In-reply-to: <19980727152658.A24276@mars.hsc.fr> References: <19980725155148.43084@mcs.net>; from Karl Denninger on Sat, Jul 25, 1998 at 03:51:48PM -0500 X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Jul 25, 1998 at 03:51:48PM -0500, Karl Denninger wrote: > > I believe I have found a rather serious MMAP problem in -CURRENT. > > > > Diablo (the news system) is the test case; with MMAP enabled it will randomly > > write exactly one block (512 bytes) of zeros into the article spool files > > rather than the proper data - its almost like an update via MMAP isn't > > I have seen an extremely similar problem, both on 2.2.6 and > -current, with INN 2.0 configured to use MMAP for the active file. > It is fairly easy to reproduce by doing a "ctlinnd newgroup". After > that, a bunch of zeroes appears in the active file. > > I haven't bothered investigating the problem for lack of time > because configuring INN to use read() just works and because I > wasn't sure it was a FreeBSD problem, but I'm ready to do any > testing I can to help fix this. > -- Ditto same problem with inn on -2.2.5, and inn 1.5.2. I seem to remember that this was documented in the inn instructions? Duncan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message