>The error message is saying the find command isn't found?
No it isn't.
>Even if it didn't find your file, there should be plenty of others
>matching that pattern.
No, it won't.
>I can only assume the message read the command wasn't found, which case it
>is a path problem or library problem.
>J.
Nope. Take a good look at what the original poster entered for the query.
>On Wed, 3 Nov 1999, Mike Friedrichs wrote:
>
>> I have a executable file called jstar in /usr/bin, but when I enter 'find
>> / -iname j*' I receive the message 'not found'.
>>
>> Is there any obvious reasons why this command doesn't function as
>> prescribed. This is on Redhat 5.2.
OK, see it yet?
No? Well, the wildcard character (*) is being substitute matched via the
command line parser, i.e., the shell. In other words, the shell is trying
to find all currect directory names that start with the letter "j", which
it didn't. And if you were in a directory that had names starting with
"j", find would have complained about a syntax error if there was more
than one name.
For programs like find, you have to protect wildcard from the shell by
enclosing them in double-quotes or escaping them with a backslash.
MB
--
e-mail: [EMAIL PROTECTED]
[Where do you think Microsoft would be today if they waited]
[until their software worked? (Hyperion Bay - 10/12/98)]
Visit - URL:http://www.vidiot.com/ (Your link to Star Trek and UPN)
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
