Date: Thu, 15 Jul 1999 00:20:57 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: "Charles M. Hannum" <root@ihack.net> Cc: Matthew Dillon <dillon@apollo.backplane.com>, Noriyuki Soda <soda@sra.co.jp>, Jason Thorpe <thorpej@nas.nasa.gov>, "Brian F. Feldman" <green@FreeBSD.ORG>, 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)) Message-ID: <378CAAD9.AAD7268E@newsguy.com> References: <199907132346.TAA13780@bikini.ihack.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?378CAAD9.AAD7268E>