Date: Wed, 14 Jul 1999 07:15:26 +0900 (JST) From: Noriyuki Soda <soda@sra.co.jp> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Noriyuki Soda <soda@sra.co.jp>, Jason Thorpe <thorpej@nas.nasa.gov>, "Brian F. Feldman" <green@FreeBSD.ORG>, bright@rush.net, dcs@newsguy.com, freebsd-hackers@FreeBSD.ORG, jon@oaktree.co.uk, tech-userlevel@netbsd.org Subject: Re: Replacement for grep(1) (part 2) Message-ID: <199907132215.HAA15042@srapc342.sra.co.jp> In-Reply-To: <199907132153.OAA81153@apollo.backplane.com> References: <199907132127.OAA80947@apollo.backplane.com> <199907132139.GAA14890@srapc342.sra.co.jp> <199907132153.OAA81153@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Tue, 13 Jul 1999 14:53:43 -0700 (PDT), Matthew Dillon <dillon@apollo.backplane.com> said: > If you are talking about a user intentionally attempting to run > a system out of swap, it is fairly easy to do whether the system > uses an overcommit model or not. The user has any number of > ways of blowing the server up too - for example, by making > thousands of connections to it or running many huge queries in > parallel. If the kernel and the application behave properly, critical application doesn't lose it's data in such situation on non-overcommiting systems. Your example doesn't make sense. -- soda 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?199907132215.HAA15042>