From owner-freebsd-hackers Wed Jul 14 22:45: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles537.castles.com [208.214.165.101]) by hub.freebsd.org (Postfix) with ESMTP id D8C7314BE3 for ; Wed, 14 Jul 1999 22:45:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA00420; Wed, 14 Jul 1999 22:40:57 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907150540.WAA00420@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: Jason Thorpe , Matthew Dillon , freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org Subject: Re: Replacement for grep(1) (part 2) In-reply-to: Your message of "Thu, 15 Jul 1999 12:58:21 +0900." <378D5C5D.13C65239@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 14 Jul 1999 22:40:57 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > And what do you do, then, with the processes that happen to have > legitimate use for more stack? > > Or maybe you just find out how much stack each process uses, and > then set limits appropriate for each one? Which is the equivalent of > setting limits to each user, of course... You get a little program, like eg. Xenix and Minix had, which lets you modify the executable header to indicate how much stack the system should reserve. If the program decides to use more stack for some reason, then it dies; this is in effect "stack overcommit". 8) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message