From owner-freebsd-stable@FreeBSD.ORG Tue Feb 15 02:41:41 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7901216A4CE for ; Tue, 15 Feb 2005 02:41:41 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33B4843D1F for ; Tue, 15 Feb 2005 02:41:41 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A173151432; Mon, 14 Feb 2005 18:41:39 -0800 (PST) Date: Mon, 14 Feb 2005 18:41:39 -0800 From: Kris Kennaway To: John Message-ID: <20050215024139.GA97764@xor.obsecurity.org> References: <20050215012633.M48733@reiteration.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline In-Reply-To: <20050215012633.M48733@reiteration.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: swapfile being eaten by unknown process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 02:41:41 -0000 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 15, 2005 at 01:30:42AM +0000, John wrote: > Hello list >=20 > Is there a way of seeing *what* program/process is eating swap. There are > loads of ways of seeing that it is being eaten, but so far haven't found = a way > of knowing what eats, so can't fix the problem. Can anyone enlighten me? Use ps or top, and look for the process with the huge size. This is not foolproof, because a process can allocate memory without using it (e.g. rpc.statd), but it's a place to start. If you see a process that is both large, and paging to/from disk, that's a better indication. Kris --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCEWFjWry0BWjoQKURAsdFAKCu5O1jpALYXu8TAT+Tcc+6NP+J5wCgrhoT 3Q2IghLwU7T7Vz93FCgAMog= =RXUa -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL--