From owner-freebsd-questions Mon Aug 11 19:30:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA18569 for questions-outgoing; Mon, 11 Aug 1997 19:30:20 -0700 (PDT) Received: from max.roskildebc.dk (max.roskildebc.dk [194.182.101.4]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA18558 for ; Mon, 11 Aug 1997 19:30:14 -0700 (PDT) Received: by max.roskildebc.dk (5.61/9.8) with UUCP id AA06330; Tue, 12 Aug 97 04:23:27 +0200 Received: by swimsuit.roskildebc.dk (0.99.970109) id AA00740; 12 Aug 97 04:17:24 +0100 From: Mike.Tancsa@234-49-99.swimsuit.roskildebc.dk (Mike Tancsa) Date: 09 Aug 97 19:14:00 +0100 Subject: expireover eating huge gobs of memory (138meg ?) Message-Id: <753_9708120417@swimsuit.roskildebc.dk> Organization: Fidonet: Swimsuit Safari <-> Internet Gateway To: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From: mike@sentex.net (Mike Tancsa) Subject: expireover eating huge gobs of memory (138meg ?) 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 -- |Fidonet: Mike Tancsa 2:234/49.99 |Internet: Mike.Tancsa@234-49-99.swimsuit.roskildebc.dk | Standard disclaimer: The views of this user are strictly his own.