From owner-freebsd-hackers Mon Jul 12 16:56: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell17.ba.best.com (shell17.ba.best.com [206.184.139.149]) by hub.freebsd.org (Postfix) with ESMTP id D8CA014EA6 for ; Mon, 12 Jul 1999 16:56:03 -0700 (PDT) (envelope-from toddpw@shell17.ba.best.com) Received: (from toddpw@localhost) by shell17.ba.best.com (8.9.3/8.9.2/best.sh) id QAA01022; Mon, 12 Jul 1999 16:55:38 -0700 (PDT) From: Todd Whitesel Message-Id: <199907122355.QAA01022@shell17.ba.best.com> Subject: Re: Replacement for grep(1) (part 2) In-Reply-To: <1336.931774684@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jul 12, 99 03:18:04 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Mon, 12 Jul 1999 16:55:38 -0700 (PDT) Cc: jon@oaktree.co.uk, dcs@newsguy.com, freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org, tech@openbsd.org X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yuck. That's a complete abomination. What's the point of it? It's turning > > Paging Terry Lambert, Terry Lambert - do you read me? It's time for > your annual rant on the topic of memory overcommit. :-) It's not overcommit so much as it is what happens to a process that gets a page fault when there are no available pages to 'fix up' the overcommit. AIX began overcommitting at one point but would kill -9 any process that page faulted when there were no available pages. AIX sysadmins universally hated this behavior and allocated HUGE swap files to avoid it. I assume FreeBSD does something more reasonable. Todd Whitesel toddpw @ best.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message