From owner-freebsd-hackers Wed Jul 14 8:24:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 0B32F14C2F; Wed, 14 Jul 1999 08:24:54 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA00262; Thu, 15 Jul 1999 00:24:44 +0900 (JST) Message-ID: <378CAAD9.AAD7268E@newsguy.com> Date: Thu, 15 Jul 1999 00:20:57 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Charles M. Hannum" Cc: Matthew Dillon , Noriyuki Soda , Jason Thorpe , "Brian F. Feldman" , bright@rush.net, freebsd-hackers@FreeBSD.ORG, jon@oaktree.co.uk, tech-userlevel@netbsd.org Subject: Re: Swap overcommit (was Re: Replacement for grep(1) (part 2)) References: <199907132346.TAA13780@bikini.ihack.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Charles M. Hannum" wrote: > > That's also objectively false. Most such environments I've had > experience with are, in fact, multi-user systems. As you've pointed > out yourself, there is no combination of resource limits and whatnot > that are guaranteed to prevent `crashing' a multi-user system due to > overcommit. My simulation should not be axed because of a bug in > someone else's program. (This is also not hypothetical. There was a > bug in one version of bash that caused it to consume all the memory it > could and then fall over.) 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. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Would you like to go out with me?" "I'd love to." "Oh, well, n... err... would you?... ahh... huh... what do I do next?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message