Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs
Date: Mon, 29 Jan 2001 11:08:38 -0600 (CST)
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
To: Daniel Barclay <Daniel DOT Barclay AT digitalfocus DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: long command lines
In-Reply-To: <3A7591C4.196574FA@digitalfocus.com>
Message-ID: <Pine.HPP.3.96.1010129110428.27153B-100000@hp2.xraylith.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 29 Jan 2001, Daniel Barclay wrote:

> I thought GNU software tried to avoid arbitrary limit like that.  Shouldn't
> the only limit be virtual memory?  

The maximum length of the argument vector is typically determined by the
underlying OS kernel interface; even if your user-level software such
as the shell supports say 100 KB long argument vector, it's still limited 
by what the kernel limit is. In Cygwin's case, Windows limits the length,
not Cygwin.

However, note that most (all?) exisiting OSs have these predefined limits
mostly for efficiency. The limits could be very large of course, or settable
at boot time, but it's there. The max number of open file descriptors is
one of the typical examples.

> That is, shouldn't bash keep reallocating (enlarging) its buffer until the
> pattern has been expanding, or until it runs out of memory?

Bash handles long command lines just fine.

Regards,
Mumit



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple