From owner-freebsd-questions  Sun Aug 10 21:44:30 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA10372
          for questions-outgoing; Sun, 10 Aug 1997 21:44:30 -0700 (PDT)
Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10366
          for <questions@FreeBSD.ORG>; Sun, 10 Aug 1997 21:44:28 -0700 (PDT)
Received: from gravel.sentex.ca (gravel.sentex.ca [205.211.165.210]) by granite.sentex.net (8.8.6/8.6.9) with SMTP id AAA23260 for <questions@FreeBSD.ORG>; Mon, 11 Aug 1997 00:54:47 -0400 (EDT)
From: mike@sentex.net (Mike Tancsa)
To: questions@FreeBSD.ORG
Subject: Re: FreeBSD 2.2 eating gobs of memory
Date: Mon, 11 Aug 1997 04:42:42 GMT
Message-ID: <33ee97c3.131423667@mail.sentex.net>
References: <3.0.2.32.19970810183410.00ade590@sentex.net>
In-Reply-To: <3.0.2.32.19970810183410.00ade590@sentex.net>
X-Mailer: Forte Agent .99e/32.227
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


>Ever since upgrading to FreeBSD 2.2-STABLE, expireover -s seems to go
>nuts and eats up huge gobs of memory that I had not seen happen before
>on 2.1.5

I think I have found the problem... It seems that control.cancel had
an overview file of 150meg! I will know for certain in the AM after
the news.daily runs tonight, and then an expireover -s in the AM after
that.

	--Mike