From owner-freebsd-hackers Tue Jan 7 10:56:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA04475 for hackers-outgoing; Tue, 7 Jan 1997 10:56:20 -0800 (PST) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA04470 for ; Tue, 7 Jan 1997 10:56:18 -0800 (PST) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.4/8.8.4) id NAA11433; Tue, 7 Jan 1997 13:52:18 -0500 (EST) From: Charles Henrich Message-Id: <199701071852.NAA11433@crh.cl.msu.edu> Subject: Re: INN redux... Re: MMAP Troubles (Joerg?) To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Tue, 7 Jan 1997 13:52:18 -0500 (EST) Cc: terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org In-Reply-To: from Jaye Mathisen at "Jan 7, 97 09:40:18 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As I was a whiner about this problem several months ago, let me step in > now by saying that INN 1.5.1 with the MSYNC stuff that was added in, has > been running just peachy under FreeBSD-current (3.0), with MMAP enabled. > > I have had none of the problems that I had before under I think 2.1. > > Methinks (and other comments bear this out), that the addition of the > MSYNC code seems to fix the problem. > > Perhaps the possibility for the condition still exists, but it doesn't > seem to be happening on a moderately busy server. I've been running with msync on a 2.2-BETA system thats been not too busy and the problem hasnt reoccured. I'll let everyone know if it does when I go into large production with this sytem. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich