Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 14 Nov 2002 10:34:12 -0600
From:	wayne <wayne AT reliant DOT immure DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: problem with bash
Message-ID:	<20021114103412.A36130@reliant.immure.com>
Reply-To:	Wayne Willcox <wayne AT reliant DOT immure DOT com>
References:	<C1256C71 DOT 00374F6E DOT 00 AT james> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20021114082348 DOT 0200b050 AT pop3 DOT cris DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<5.1.0.14.2.20021114082348.0200b050@pop3.cris.com>; from rrschulz@cris.com on Thu, Nov 14, 2002 at 08:29:27AM -0800
X-Operating-System:	FreeBSD reliant.immure.com 4.4-RELEASE FreeBSD 4.4-RELEASE

Here is an example..

find . -type f |xargs ls

I came in late and this might not be a solution to your exact 
problem but it might at least help get you on the right path.


On Thu, Nov 14, 2002 at 08:29:27AM -0800, Randall R Schulz wrote:
> Claudio,
> 
> No, that's not a bug. It's just a (system-dependent) limit shared by all 
> POSIX-compliant systems. The actual limit happens to be on the low side 
> under Cygwin.
> 
> Familiarize yourself with the "xargs" command. It's there just to handle 
> these cases.
> 
> Also, in many cases the programs themselves process directories and don't 
> need to have each file within the directory passed to them as an argument. 
> Ls certainly does this (hence your "ls *" example has an equivalent without 
> limits: plain old "ls") and the grep family has a -R (recursive) option 
> that's related.
> 
> The reason you don't see the problem from a DOS command prompt is that 
> argument handling (in particular, wild-card processing) is different when 
> Cygwin programs are invoked from a DOS CMD.exe or Command.exe shell and 
> that difference effectively side-steps the limit you experience when 
> running under a Cygwin shell (BASH, zsh, tcsh, ash, etc.).
> 
> Good luck.
> 
> Randall Schulz
> Mountain View, CA USA
> 
> 
> At 01:59 2002-11-14, Claudio Tamietto wrote:
> >I have installed cigwin on my W2K PC and all is very well functioning .
> >However if i try some commands like ls * or grep -i -l some_text * from a
> >directory whit a lot of files (7-8 thousand) i obtain this error
> >
> >bash: /usr/bin/ls: Invalid argument
> >
> >Is it a bug ?
> >
> >If i try the same commands from a dos shell the error is not reported and 
> >all is functioning .
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/

-- 
Slowly and surely the unix crept up on the Nintendo user ...
Wayne Willcox                          I will not eat green eggs and ham
wayne AT reliant DOT immure DOT com                     I will not eat them Sam I Am!!
A wise person makes his own decisions, a weak one obeys public opinion.
                -- Chinese proverb

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -