From owner-freebsd-isp Wed Jul 9 15:01:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA14857 for isp-outgoing; Wed, 9 Jul 1997 15:01:38 -0700 (PDT) Received: from mail1.sirius.com (mail1.sirius.com [205.134.253.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA14847 for ; Wed, 9 Jul 1997 15:01:34 -0700 (PDT) Received: from ds9.sirius.com (ds9.sirius.com [205.134.226.34]) by mail1.sirius.com (8.8.6/Sirius-8.8.6-97.06.26) with ESMTP id PAA09019 for ; Wed, 9 Jul 1997 15:01:33 -0700 (PDT) Received: from localhost (dlowe@localhost) by ds9.sirius.com (8.6.12/961127) with SMTP id PAA16151 for ; Wed, 9 Jul 1997 15:01:40 -0700 X-Authentication-Warning: ds9.sirius.com: dlowe owned process doing -bs Date: Wed, 9 Jul 1997 15:01:39 -0700 (PDT) From: David Lowe X-Sender: dlowe@ds9 Reply-To: David Lowe To: freebsd-isp@freebsd.org Subject: INN on an async-mounted spool? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk People - Has anyone here tried INN on an async-mounted spool in production? Our news server (FreeBSD 2.2.2, INN 1.5.1) is running consistently a few hours behind with a synchronous spool, and we've tried it with async mounts & had it run *much* faster - able to pull in ~520 articles per minute from our single feed (a Diablo machine) (as opposed to ~380, which is not quite enough these days to ensure keeping up with a full feed.) We're not too concerned about data loss on the spool in the event of a failure - but we *are* concerned about the async option actually *causing* crashes. While we were running async, we had two mysterious crashes (which of course led to some data loss & required human intervention for fsck'ing). Since we've gone synchronous, we've not had these mystery crashes (knock wood) but we've also not been able to keep up as nicely as we'd like to. Has anyone had success with an async-mounted spool in the long term? Pros? Cons? Thanks, David Lowe