From owner-freebsd-hackers Wed Jul 14 3:49: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay02.indigo.ie (relay02.indigo.ie [194.125.133.226]) by hub.freebsd.org (Postfix) with SMTP id B5F2B14D8D for ; Wed, 14 Jul 1999 03:49:03 -0700 (PDT) (envelope-from niall@pobox.com) Received: (qmail 13377 messnum 46325 invoked from network[194.125.220.235/ts06-108.dublin.indigo.ie]); 14 Jul 1999 10:47:40 -0000 Received: from ts06-108.dublin.indigo.ie (HELO pobox.com) (194.125.220.235) by relay02.indigo.ie (qp 13377) with SMTP; 14 Jul 1999 10:47:40 -0000 Message-ID: <378C85DB.70488160@pobox.com> Date: Wed, 14 Jul 1999 12:43:07 +0000 From: Niall Smart X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: Jason Thorpe , freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org Subject: Re: Replacement for grep(1) (part 2) References: <199907132328.QAA25285@lestat.nas.nasa.gov> <199907132333.QAA82004@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Maybe if I call the sysctl "vm.crashmenow". No, that will just make more > people actually try it. It might be doable as a compile-time option, > since you wouldn't be able to run anything approaching standard on > such a system anyway. I don't see much use for it myself. As I said > before, there are easier ways to manage memory that are not quite as > arbitrary as simply refusing a potential overcommit. Perhaps it could be an additional flag to mmap, in this way people wishing to run an overcommited system could do so but those writing programs which must not overcommit for certain memory allocations could ensure they did not do so. Regards, Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message