From owner-freebsd-questions Sat Aug 9 10:16:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA03068 for questions-outgoing; Sat, 9 Aug 1997 10:16:12 -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 KAA03063 for ; Sat, 9 Aug 1997 10:16:09 -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 NAA21079 for ; Sat, 9 Aug 1997 13:26:16 -0400 (EDT) From: mike@sentex.net (Mike Tancsa) To: questions@freebsd.org Newsgroups: news.software.nntp Subject: expireover eating huge gobs of memory (138meg ?) Date: Sat, 09 Aug 1997 17:14:00 GMT Message-ID: <33eca46b.3591073@news.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 PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 2181 news 56 0 18204K 6128K RUN 7:14 28.72% 28.72% innd 2245 news 88 20 138M 84540K RUN 2:28 5.72% 5.72% expireover Any idea whats going on here ? Thanks, ---Mike