From owner-freebsd-hackers Wed Jul 14 8:30:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pzero.sandelman.ottawa.on.ca (gigabit.solidum.com [216.13.130.242]) by hub.freebsd.org (Postfix) with ESMTP id 97BC814CBA for ; Wed, 14 Jul 1999 08:30:09 -0700 (PDT) (envelope-from mcr@sandelman.ottawa.on.ca) Received: from morden.sandelman.ottawa.on.ca (localhost [127.0.0.1]) by pzero.sandelman.ottawa.on.ca (8.8.8/8.8.8) with ESMTP id JAA04832; Wed, 14 Jul 1999 09:24:02 -0400 (EDT) Message-Id: <199907141324.JAA04832@pzero.sandelman.ottawa.on.ca> To: freebsd-hackers@freebsd.org, tech-userlevel@netbsd.org Subject: Re: Replacement for grep(1) (part 2) In-reply-to: Your message of "Tue, 13 Jul 1999 16:33:41 PDT." <199907132333.QAA82004@apollo.backplane.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Wed, 14 Jul 1999 09:20:52 -0400 From: Michael Richardson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Matthew" == Matthew Dillon writes: Matthew> Maybe if I call the sysctl "vm.crashmenow". No, that will just make more Matthew> people actually try it. It might be doable as a compile-time option, Matthew> since you wouldn't be able to run anything approaching standard on Matthew> such a system anyway. I don't see much use for it myself. As I said Matthew> before, there are easier ways to manage memory that are not quite as Matthew> arbitrary as simply refusing a potential overcommit. Is there anyway on FreeBSD to a) ask that one not be on the SIGKILL list? b) tune the amount of overcommit? ] Train travel features AC outlets with no take-off restrictions| firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[ ] panic("Just another NetBSD/notebook using, kernel hacking, security guy"); [ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message