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
Message-ID:	<3A7591C4.196574FA@digitalfocus.com>
Date:	Mon, 29 Jan 2001 10:52:36 -0500
From:	Daniel Barclay <Daniel DOT Barclay AT digitalfocus DOT com>
X-Mailer:	Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: long command lines
References:	<3A70B734 DOT A18289E AT nuance DOT com> <3A70C7CB DOT AB0DA2BE AT yahoo DOT com>

Earnie Boyd wrote:
> 
> Mike Schuster wrote:
> >
> > Problem: I couldn't figure out how to get very long command line
> > arguments to work (~32k) (for example 'ls */*/*/*', if you have a lot of
> > files on the disk).
...
> 
> Well, most systems have a command line limit.  Check out `man xargs'.
> However, xargs may have limits also.

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

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

Daniel
-- 
Daniel Barclay
Digital Focus
Daniel DOT Barclay AT digitalfocus DOT com

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

- Raw text -