From owner-freebsd-hackers  Mon Mar 10 00:59:56 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA04737
          for hackers-outgoing; Mon, 10 Mar 1997 00:59:56 -0800 (PST)
Received: from thelab.hub.org ([207.107.138.222])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA04726
          for <hackers@freebsd.org>; Mon, 10 Mar 1997 00:59:53 -0800 (PST)
Received: from thelab.hub.org (localhost [127.0.0.1]) by thelab.hub.org (8.8.5/8.8.2) with SMTP id EAA07193; Mon, 10 Mar 1997 04:59:45 -0400 (AST)
Date: Mon, 10 Mar 1997 04:59:45 -0400 (AST)
From: The Hermit Hacker <scrappy@hub.org>
To: Tom Samplonius <tom@sdf.com>
cc: Joe McGuckin <joe@via.net>, hackers@freebsd.org
Subject: Re: freebsd as a news server?
In-Reply-To: <Pine.NEB.3.94.970309230624.6880D-100000@misery.sdf.com>
Message-ID: <Pine.BSF.3.95.970310045911.4273Q-100000@thelab.hub.org>
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, Tom Samplonius wrote:

> 
> 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.
>
	This is, of course, assuming that Joe is using the 'delayrm' option,
which it sounds like he isn't/wasn't, if expire was running 18hrs...