From owner-freebsd-current Mon Mar 27 00:00:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA13204 for current-outgoing; Mon, 27 Mar 1995 00:00:23 -0800 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA13190 for ; Mon, 27 Mar 1995 00:00:20 -0800 Received: by pelican.com (Smail3.1.28.1 #5) id m0rt9iW-000K0iC; Mon, 27 Mar 95 00:00 WET Message-Id: Date: Mon, 27 Mar 95 00:00 WET From: pete@pelican.com (Pete Carah) To: current@FreeBSD.org Subject: Re: Innd In-Reply-To: References: <199503231719.TAA23687@katiska.clinet.fi> <9503231915.AA08773@blaise.ibp.fr> <199503261709.UAA08986@zetor.clinet.fi> Organization: Pelican Consulting Sender: current-owner@FreeBSD.org Precedence: bulk ... >> > Don't use ACT_MMAP in config.data for the reading of the active file. >>Removed MMAP, and it seems to be stable now. In article ache writes: >All this mess comes becomes msync() and munmap() don't update >modification times at all. That may not be the only reason - note that innd cores about once/day on an sgi indigo under 4.0.5 if mmap is used, and runs for months without it, and there mmap behaves supposedly OK (and it really was the only change). Either innd doesn't really handle mmap right or sgi isn't much better than we are :-) (and I've taken to not using mmap-active at all...) -- Pete