Re: bug? in find

[Marcel Martin]

On Wednesday 16 October 2002 04:35, Shigeru Mabuchi wrote:
> Hello,
[...]
>   For example, if there are only files in the
> directory /home/foo/obj,
>
>   find /home/foo/obj -name *.o
>
> returns the above error.
>
> Instead,
>
>   find /home/foo -name *.o
>
> gives me the *.o list in /home/foo/obj.
>
>   I'm not sure if this is a part of the 'find'
> specs, but even if it is so, I believe that it
> should be corrected. At least the error message
> should be something like 'no directory found'
> if 'find' can only search directory in the top
> level of the search path.

Please try to add double or single quotes to the search pattern like this:
find /home/foo/obj -name '*.o'
If you don't, your shell will replace *.o with a list of all .o-files in the 
current directory (if there are any).
You might need to provide a more accurate description of how to reproduce your 
problem if this doesn't solve it.

>   Thanks.
>
> Shigeru MABUCHI
> WING
> http://wing.gr.jp/

Greetings,
Marcel
-- 
 . .
/ V / Marcel Martin   Bielefeld   OpenPGP public key:
\   \ address@hidden Germany     http://w148.de/~mmartin/public-key.asc