bash /usr/bin/ls invalid argument

bash /usr/bin/ls invalid argument

[Jared Ingersoll]

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/

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

RE: bash /usr/bin/ls invalid argument

[Hannu E K Nevalainen]

> From: Jared Ingersoll
> Sent: Monday, October 27, 2003 8:55 PM

> 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

 For newbies: to get to grips about how this works "under the hood"; read up
on how "Shell expansion" works in e.g. bash (i.e. search and read the "man"
or "info" on bash)

 IIRC there was a recent thread (about environment variables and passing
arguments to a windows-console program):

There is a 32KB length limit on the command line. This is imposed on us by
the underlying "OS" - i.e. not likely to change.


To check how long your command line would be, try something like this:

$ find -type f -name 'send.log.*' |
(
  read f;
  cc=-1;
  echo "";
  while [ ! -z "$f" ];do
    cc=$(( 1 + $cc + $( echo "$f" | wc -c) ));
    echo -e "\e[F$cc\e[K";read f;
  done;
  echo -e "\e[F$cc chars"
)

Remember to add the length of e.g. "ls -l " (note space).

If this gives a number larger than...

$ echo $(( ( 1 << 15 ) -1 ))
32767

... then you're "outta luck".

/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- printf("Timezone: %s\n", (DST)?"UTC+02":"UTC+01"); --
--END OF MESSAGE--


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

Re: bash /usr/bin/ls invalid argument

[Nicolas BUONOMO]

Hello,

Hannu E K Nevalainen a écrit :

>>From: Jared Ingersoll
>>Sent: Monday, October 27, 2003 8:55 PM
> 
> ....
> 
> There is a 32KB length limit on the command line. This is imposed on us by
> the underlying "OS" - i.e. not likely to change.
> 
> 
> To check how long your command line would be, try something like this:
> 
> $ find -type f -name 'send.log.*' |
> (
>   read f;
>   cc=-1;
>   echo "";
>   while [ ! -z "$f" ];do
>     cc=$(( 1 + $cc + $( echo "$f" | wc -c) ));
>     echo -e "\e[F$cc\e[K";read f;
>   done;
>   echo -e "\e[F$cc chars"
> )
> 
> Remember to add the length of e.g. "ls -l " (note space).
> 
> If this gives a number larger than...
> 
> $ echo $(( ( 1 << 15 ) -1 ))
> 32767
> 
> ... then you're "outta luck".
> 

I try your command on a Microsoft XP pro and I win

nicolas@cl12369n ~ s=1
  $ find -type f -name '*' | (   read f;   cc=-1;   echo "";   while
[ ! -z "$f" ]; do     cc=$(( 1 + $cc + $( echo "$f" | wc -c) ));
  echo -e "\e[F$cc\e[K";read f;   done;   echo -e "\e[F$cc chars"; )
1789980 chars

Where is the problem?

bye

> /Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
> -- printf("Timezone: %s\n", (DST)?"UTC+02":"UTC+01"); --
> --END OF MESSAGE--
> 
> 
> --
> 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/
> 
> 
> 

RE: bash /usr/bin/ls invalid argument

[Hannu E K Nevalainen]

> From: Nicolas BUONOMO
> Sent: Wednesday, October 29, 2003 9:52 AM

> Hello,
>
> Hannu E K Nevalainen a écrit :
>
> >>From: Jared Ingersoll
> >>Sent: Monday, October 27, 2003 8:55 PM
> >
> > ....
> >
> > There is a 32KB length limit on the command line. This is
> imposed on us by
> > the underlying "OS" - i.e. not likely to change.
> >
> >
> > To check how long your command line would be, try something like this:
> >
> > $ find -type f -name 'send.log.*' |
> > (
> >   read f;
> >   cc=-1;
> >   echo "";
> >   while [ ! -z "$f" ];do
> >     cc=$(( 1 + $cc + $( echo "$f" | wc -c) ));
> >     echo -e "\e[F$cc\e[K";read f;
> >   done;
> >   echo -e "\e[F$cc chars"
> > )
> >
> > Remember to add the length of e.g. "ls -l " (note space).
> >
> > If this gives a number larger than...
> >
> > $ echo $(( ( 1 << 15 ) -1 ))
> > 32767
> >
> > ... then you're "outta luck".
> >
>
> I try your command on a Microsoft XP pro and I win
>
> nicolas@cl12369n ~ s=1
>   $ find -type f -name '*' | (   read f;   cc=-1;   echo "";   while
> [ ! -z "$f" ]; do     cc=$(( 1 + $cc + $( echo "$f" | wc -c) ));
>   echo -e "\e[F$cc\e[K";read f;   done;   echo -e "\e[F$cc chars"; )
> 1789980 chars
>
> Where is the problem?
>

 =-) there is no problem with _my_ command. It was to show _when_ there is a
problem - and what the problem consists of.

 Try "ls -l *" in the same directory as you did your test in. That will give
you an error message, due to the limit mentioned earlier in this thread.

/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- printf("LocalTime: UTC+%02d\n",(DST)? 1:2); --
--END OF MESSAGE--


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

Re: bash /usr/bin/ls invalid argument

[Christopher Faylor]

On Tue, Oct 28, 2003 at 07:02:15AM -0500, Jared Ingersoll wrote:
>Thanks, I thought it may be something inherent. I can work around this
>limitation.

Let me again point out that there is a way around this limitation:

http://sources.redhat.com/ml/cygwin/2003-09/msg01607.html
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam@sourceware.org
and be permanently blocked from mailing lists at sources.redhat.com

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

RE: bash /usr/bin/ls invalid argument

[Jared Ingersoll]

Thanks, I thought it may be something inherent. I can work around this
limitation.

Jared

-----Original Message-----
From: Hannu E K Nevalainen [mailto:garbage_collector@telia.com]
Sent: Tuesday, October 28, 2003 5:20 AM
To: cygwin@cygwin.com
Subject: RE: bash /usr/bin/ls invalid argument


> From: Jared Ingersoll
> Sent: Monday, October 27, 2003 8:55 PM

> 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

 For newbies: to get to grips about how this works "under the hood"; read up
on how "Shell expansion" works in e.g. bash (i.e. search and read the "man"
or "info" on bash)

 IIRC there was a recent thread (about environment variables and passing
arguments to a windows-console program):

There is a 32KB length limit on the command line. This is imposed on us by
the underlying "OS" - i.e. not likely to change.


To check how long your command line would be, try something like this:

$ find -type f -name 'send.log.*' |
(
  read f;
  cc=-1;
  echo "";
  while [ ! -z "$f" ];do
    cc=$(( 1 + $cc + $( echo "$f" | wc -c) ));
    echo -e "\e[F$cc\e[K";read f;
  done;
  echo -e "\e[F$cc chars"
)

Remember to add the length of e.g. "ls -l " (note space).

If this gives a number larger than...

$ echo $(( ( 1 << 15 ) -1 ))
32767

... then you're "outta luck".

/Hannu E K Nevalainen, B.Sc. EE - 59?16.37'N, 17?12.60'E
-- printf("Timezone: %s\n", (DST)?"UTC+02":"UTC+01"); --
--END OF MESSAGE--


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

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