From owner-freebsd-hackers  Sun Mar  9 23:10:34 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA11282
          for hackers-outgoing; Sun, 9 Mar 1997 23:10:34 -0800 (PST)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA11268
          for <hackers@freebsd.org>; Sun, 9 Mar 1997 23:10:30 -0800 (PST)
Received: from misery.sdf.com [204.244.213.33] 
	by misery.sdf.com with smtp (Exim 1.59 #1)
	id 0w3zDm-0002aU-00; Sun, 9 Mar 1997 23:10:10 -0800
Date: Sun, 9 Mar 1997 23:10:10 -0800 (PST)
From: Tom Samplonius <tom@sdf.com>
To: Joe McGuckin <joe@via.net>
cc: hackers@freebsd.org
Subject: Re: freebsd as a news server?
In-Reply-To: <199703100431.UAA05566@monk.via.net>
Message-ID: <Pine.NEB.3.94.970309230624.6880D-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Sun, 9 Mar 1997, Joe McGuckin wrote:

> I was having the same problem with expire taking over 18 hours to complete.

  Ok.  For the *entire* expiration process, right?

> Someone suggested forcing expire to rebuild the history database using a 
> different spindle for temp space.
> 
> That fixed it. Now the history rebuild finishes in under 5 minutes.

  Errr... but the history rebuild is always the easiest and fastest part
of the expiration process.  The fastrm and expireover is the time
consuming part.

> Joe

Tom