From owner-freebsd-isp Fri Sep 12 08:52:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA12249 for isp-outgoing; Fri, 12 Sep 1997 08:52:26 -0700 (PDT) Received: from yacko.netgazer.net (yacko.netgazer.net [209.83.225.63]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA12241 for ; Fri, 12 Sep 1997 08:52:21 -0700 (PDT) Received: from [209.83.225.224] (furball.netgazer.com [209.83.225.224]) by yacko.netgazer.net (8.8.5/8.7.3) with ESMTP id KAA16391 for ; Fri, 12 Sep 1997 10:59:33 GMT X-Sender: rootlist@yacko.netgazer.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 12 Sep 1997 10:58:39 -0500 To: freebsd-isp@FreeBSD.ORG From: "Darrin R. Woods" Subject: INN question - expire Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've been running an INN server for about a year now and have come up with a problem that I'm not sure what is going on. Expire seems to be taking about 10-12 hours each day. This started just a few days ago after I set the expire.ctl down abit to throw things away a little quicker. It is running on a P166, 128mb, 2.2.2FBSD, INN 1.5.1 with overchan. Expire never took this long before and has been running for about 10 hours or so for 3 days now. I changed it from: *:A:1:5:9 to *:A:1:4:7 According to the reports and the disk usage, I'm don't that much more news than before, it just seems to be taking longer. Here's my cron job: 40 2 * * * /usr/local/news/bin/news.daily delayrm expireover Any ideas of what might be causing it to take so long? Thanks in advance Darrin R. Woods | "Will Work for Bandwidth" Director of Operations | Netgazer Solutions, Inc. | Dallas, Texas 972.702.9119 | work: http://www.netgazer.net My employer most whole-heartedly denies everything I say