From owner-freebsd-hackers Tue Jul 13 14:40:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (Postfix) with ESMTP id 8EDFB152CD for ; Tue, 13 Jul 1999 14:40:14 -0700 (PDT) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id OAA24282; Tue, 13 Jul 1999 14:38:49 -0700 (PDT) Message-Id: <199907132138.OAA24282@lestat.nas.nasa.gov> To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org Subject: Re: Replacement for grep(1) (part 2) Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 13 Jul 1999 14:38:49 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 13 Jul 1999 14:27:54 -0700 (PDT) Matthew Dillon wrote: > You are assuming that the situation actually occurs. In real life, > it will not occur unless the critical server is running away with > memory. > > I have never, ever run one of BEST's servers out of swap. It has never > been an issue. In BEST's critical servers, maybe that's true. But applying your experience at BEST to the wide range of UNIX users is ... a bit ridiculous, I think :-) > And, I can only repeat, again, that long before a reasonably configured > FreeBSD system runs out of swap it would become unusable from the I/O > overload. See previous point: "who said we were even going to swap *at all*?" You're making a lot of assumptions about the sort of programs people run on BSD systems, not all of which are reasonable to make. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message