Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <3A7591C4.196574FA@digitalfocus.com> Date: Mon, 29 Jan 2001 10:52:36 -0500 From: Daniel Barclay X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: long command lines References: <3A70B734.A18289E@nuance.com> <3A70C7CB.AB0DA2BE@yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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.Barclay@digitalfocus.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple