Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-ID: <39185ABF.EA1EAE77@veritas.com> Date: Tue, 09 May 2000 11:36:47 -0700 From: Bob McGowan Organization: VERITAS Software X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: David Robinow CC: cygwin@sourceware.cygnus.com Subject: Re: wildcard expansion once more References: <20000509174310.17931.qmail@web2105.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit David Robinow wrote: > > --- Andre Berton wrote: > > While processing large amounts of data, cygwin runs > > into trouble with > > wildcard expansion (it happens only while processing > > thousands of files). For example: > > ls */*.txt > > comes up with > > bash: //c/cygtools/....bin/ls: Invalid argument > > > This is a bug. It should say "Arg list too long." or > something similar. Assuming that the error was from 'ls', I'd agree. But when I run 'ls' with an invalid argument, it reports: x*x: No such file or directory It does not prepend "bash:" as seen in this error message. I would assume any other errors from 'ls' would be handled the same. I'm wondering if there is some problem with the "//c/cygtools/...bin/ls" part itself? Put another way, 'bash' is complaining about "//c/cygtools/...bin/ls" being invalid. Seems that there is a need here for some further info, such as the output of: cygcheck -r -s -v ---deleted--- -- Bob McGowan Staff Software Quality Engineer VERITAS Software rmcgowan@veritas.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com