From owner-freebsd-questions Sun Aug 10 15:36:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA20522 for questions-outgoing; Sun, 10 Aug 1997 15:36:07 -0700 (PDT) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA20482 for ; Sun, 10 Aug 1997 15:36:02 -0700 (PDT) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.6/8.8.3) with SMTP id SAA06803 for ; Sun, 10 Aug 1997 18:42:36 -0400 (EDT) Message-Id: <3.0.2.32.19970810183410.00ade590@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Sun, 10 Aug 1997 18:34:10 -0400 To: questions@freebsd.org From: Mike Tancsa Subject: FreeBSD 2.2 eating gobs of memory Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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 ? I noticed that the only real difference between the 2.2 kernel config and the 2.1.5 kernel config is that I have in the 2.2 the SYSV options turned on. Would this effect it, or is there something else going on here ? Before, I think I saw expireover -s grow to a max of 30-40meg, but never anything approaching the 138M. Thanks in advance, ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatra (http://www.sentex.net/~mdtancsa) *