From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: zsh-workers-request@euclid.skiles.gatech.edu Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by coral.primenet.com.au (8.7.6/8.7.3) with ESMTP id EAA05437 for ; Thu, 14 Nov 1996 04:59:55 +1100 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id MAA04986; Wed, 13 Nov 1996 12:42:11 -0500 (EST) Resent-Date: Wed, 13 Nov 1996 12:42:11 -0500 (EST) From: "Bart Schaefer" Message-Id: <961113094601.ZM29148@candle.brasslantern.com> Date: Wed, 13 Nov 1996 09:46:00 -0800 In-Reply-To: Peter Stephenson "Re: OPEN_MAX from sysconf" (Nov 13, 5:28pm) References: <199611131628.RAA06320@hydra.ifh.de> Reply-To: schaefer@nbn.com X-Mailer: Z-Mail (4.0b.820 20aug96) To: Peter Stephenson , zsh-workers@math.gatech.edu (Zsh hackers list) Subject: Re: OPEN_MAX from sysconf MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"aegpU3.0.qD1.oXWYo"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2395 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu On Nov 13, 5:28pm, Peter Stephenson wrote: } Subject: Re: OPEN_MAX from sysconf } } Johan Danielsson wrote: } > A lot better, but I assume that you can raise it to an arbitrary } > limit. The solution we are really looking for is something better than } > having to malloc(arbitrary number). } } You could have some maximum for the initial allocation for fdtable and } get the stuff in utils.c to allocate more if it was necessary. I don't think it's worth the effort. In practice there's always going to be *some* hard limit, even if it's in the thousands; a few thousand chars allocated isn't going to make that much difference to zsh. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.nbn.com/people/lantern