From owner-freebsd-questions Wed Jan 1 03:06:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA23485 for questions-outgoing; Wed, 1 Jan 1997 03:06:04 -0800 (PST) Received: from bbq.websource.com.au (bbq.websource.com.au [203.12.233.198]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA23479 for ; Wed, 1 Jan 1997 03:05:58 -0800 (PST) Received: from zaphod (zaphod.apnpc.com.au [203.12.233.194]) by bbq.websource.com.au (8.8.3/8.6.12) with SMTP id VAA03847 for ; Wed, 1 Jan 1997 21:20:34 GMT Message-Id: <199701012120.VAA03847@bbq.websource.com.au> Comments: Authenticated sender is From: "Mark Cheeseman" Organization: WebSource Pty Ltd To: freebsd-questions@freebsd.org Date: Tue, 31 Dec 1996 22:02:12 +1000 Subject: What's eating my memory Reply-to: cheese@websource.com.au Priority: normal X-mailer: Pegasus Mail for Windows (v2.01) Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What's the best way to diagnose a system (2.1.6.1-R) that is running out of virtual memory? I have a system here that has suddenly taken it upon itself to eat up all available memory and then (not surprisingly) refuses to do anything else. I don't recall doing anything much to it recently, so I'm at a loss to figure out what is doing the dastardly deed. Thanks (and happy new year!) -mark -- Mark Cheeseman VK2XGK cheese@asstdc.com.au cheese@apnpc.com.au Tel +61 2 9936 8689 http://www.apnpc.com.au http://www.websource.com.au