Subject: Re: Replacement for grep(1) (part 2)
To: Michael Richardson <email@example.com>
From: Brian F. Feldman <green@FreeBSD.org>
Date: 07/14/1999 12:02:56
On Wed, 14 Jul 1999, Michael Richardson wrote:
> >>>>> "Matthew" == Matthew Dillon <firstname.lastname@example.org> 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?
I think it would be better to find the process(es) trying to use memory so
voraciously and send them the SIGKILLs. This should be feasible.
> ] Train travel features AC outlets with no take-off restrictions| firewalls [
> ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
> ] email@example.com 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
Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___
green@FreeBSD.org _ __ ___ | _ ) __| \
FreeBSD: The Power to Serve! _ __ | _ \._ \ |) |
http://www.FreeBSD.org/ _ |___/___/___/