From owner-freebsd-hackers Wed Jul 14 10:18:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 40E3414E0A; Wed, 14 Jul 1999 10:18:29 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id NAA45684; Wed, 14 Jul 1999 13:17:18 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <378CAAD9.AAD7268E@newsguy.com> References: <199907132346.TAA13780@bikini.ihack.net> Date: Wed, 14 Jul 1999 13:17:14 -0400 To: "Daniel C. Sobral" From: Garance A Drosihn Subject: Re: Swap overcommit (was Re: Replacement for grep(1) (part 2)) Cc: Matthew Dillon , "Brian F. Feldman" , freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:20 AM +0900 7/15/99, Daniel C. Sobral wrote: > In which case the program that consumed all memory will be killed. > The program killed is +NOT+ the one demanding memory, it's the one > with most of it. But that isn't always the best process to have killed off... One of my main freebsd machines is mainly here to run one process, which is a pretty good-sized process (>40meg). If I did get into a memory-shortage problem, I do *not* want that process killed, I'd want some other processes killed. It would be nice to have a way to indicate that, a la SIGDANGER. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message