Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: From: "Buchbinder, Barry (NIH/NIAID)" To: "'cygwin AT cygwin DOT com'" Subject: RE: shell cmds crapping out with large numbers of files Date: Wed, 26 May 2004 09:43:18 -0400 MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes In acting on Chris and Igor's replies, Bruce should remember that there are two different command lines; the command line passed to a program and the command line within a shell. While Windows limits the command line length that is passed, a shell may not (bash doesn't), since the command line is not being passed outside of the shell. /c> echo /c/DW/out/NIAID/* | wc 1 934 36055 /c> /bin/echo /c/DW/out/NIAID/* | wc bash: /bin/echo: Arg list too long 0 0 0 /c> ls /c/DW/out/NIAID/* | wc bash: /bin/ls.exe: Arg list too long 0 0 0 /c> for F in /c/DW/out/NIAID/* ; do ls $F ; done | wc 934 934 36055 /c> echo /c/DW/out/NIAID/* | xargs ls | wc 934 934 36055 -----Original Message----- From: Christopher Faylor Sent: Tuesday, May 25, 2004 7:10 PM To: cygwin AT cygwin DOT com Subject: Re: shell cmds crapping out with large numbers of files On Tue, May 25, 2004 at 06:55:35PM -0400, Igor Pechtchanski wrote: >Cygwin has a 32k command-line length limit. Cygwin doesn't, AFAIK, have any command-line length limit other than the amount of memory available to store the command line. Windows has a limit but Cygwin shouldn't impose one. That's why I advocate using the "mount -X" option. Not only does it work around these type of things it should also speed things up slightly. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/