bash /usr/bin/ls invalid argument

[Andrew DeFaria]

Jared Ingersoll wrote:

>Hi,
>
>I'm using bash 2.05b-16 on Win2K pro and I'm running into problems listing directory contents with a wildcard. This particular directory has over 8000 files in it, most of which (99%) are files that start with send.log.*. When I issue the following commands, I get the same error:
>
>$ ls send.log.*
>bash: /usr/bin/ls: Invalid argument
>
>$ ls send.log.2003*
>bash: /usr/bin/ls: Invalid argument
>
>$ ls send.log.200307*
>bash: /usr/bin/ls: Invalid argument
>
>However, if i issuse the same command in the same directory for a different filename (amount to less that 1% of the files) it works:
>
>$ ls receive.log.2003*
>receive.log.20030703  receive.log.20030806  receive.log.20030903
>receive.log.20031001
>receive.log.20030707  receive.log.20030807  receive.log.20030904
>receive.log.20031002
>receive.log.20030708  receive.log.20030808  receive.log.20030905
>receive.log.20031003
>receive.log.20030712  receive.log.20030809  receive.log.20030906
>receive.log.20031004
>
>Any ideas what might be going on? Obviously, for scripting purposes I need to be able to list the directory contents with a wildcard (actually want to use this with grep). 
>
>$ grep IDxxxxxxxxxxxxxxxxxxxxxx send*
>bash: /usr/bin/grep: Invalid argument
>
>I tried this with the bourne shell and it seems to do the same thing.
>
man xargs.
-- 
The careful application of terror is also a form of communication.



--
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/