Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <4.3.1.2.20010129110023.022b0468@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Mon, 29 Jan 2001 11:00:47 -0500 To: Daniel Barclay , cygwin AT cygwin DOT com From: "Larry Hall (RFK Partners, Inc)" Subject: Re: long command lines In-Reply-To: <3A7591C4.196574FA@digitalfocus.com> References: <3A70B734 DOT A18289E AT nuance DOT com> <3A70C7CB DOT AB0DA2BE AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 10:52 AM 1/29/2001, Daniel Barclay wrote: >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? I'm sure you can find your answer in the source if you're interested. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple