From: Jared Ingersoll <jared@cswv.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: bash /usr/bin/ls invalid argument
Date: Tue, 28 Oct 2003 00:12:00 -0000 [thread overview]
Message-ID: <4FF77D01E13B214590F4FA3E2C3021D0873ADA@pecos.csw.alewife.net> (raw)
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.
Jared
--
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/
next reply other threads:[~2003-10-27 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 0:12 Jared Ingersoll [this message]
2003-10-28 1:13 ` Andrew DeFaria
2003-10-28 12:57 ` Hannu E K Nevalainen
2003-10-29 10:17 ` Nicolas BUONOMO
2003-10-29 15:23 ` Hannu E K Nevalainen
2003-10-28 14:08 Jared Ingersoll
2003-10-28 16:05 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FF77D01E13B214590F4FA3E2C3021D0873ADA@pecos.csw.alewife.net \
--to=jared@cswv.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).