[SOLVED] Not able to find out file

Huamin · 10-11-2015, 11:49 PM

Hi,
The file name "*wild*" should be existing within the OS, but I don't know why I get this

[root@CentOS65x64 /]# ls -R *wild* > t01.txt
ls: cannot access *wild*: No such file or directory
[root@CentOS65x64 /]#

that is being run on root folder.

Beryllos · 10-12-2015, 01:15 AM

You could use the find command. Example:

Code:

find . -name "*wild*" > t01.txt

Edit: As chrism01 wrote below, this should be written with single quotes:

Code:

find . -name '*wild*' > t01.txt

chrism01 · 10-12-2015, 01:51 AM

Re find cmd: best to use single quotes for wildcard chars like '*' as this ensures they are parsed by the find cmd, not the shell.
Otherwise, you could eg end up with 'too many args..' error.

Beryllos · 10-12-2015, 08:59 AM

Quote:

Originally Posted by chrism01

Re find cmd: best to use single quotes for wildcard chars like '*' as this ensures they are parsed by the find cmd, not the shell.
Otherwise, you could eg end up with 'too many args..' error.

Thanks. I had wondered what the difference is.

pan64 · 10-12-2015, 09:37 AM

you can simply try:
echo *wild*
echo '*wild*'
echo "*wild*"
and you will see the differences. Remember, it is the shell who evaluates * (and other chars, like ?) not the echo command.

hortageno · 10-12-2015, 09:59 AM

Quote:

Originally Posted by pan64

you can simply try:
echo *wild*
echo '*wild*'
echo "*wild*"
and you will see the differences. Remember, it is the shell who evaluates * (and other chars, like ?) not the echo command.

Hmmm, what am I missing?

Code:

$  echo *wild*
*wild*
$  echo '*wild*'
*wild*
$  echo "*wild*"
*wild*

pan64 · 10-12-2015, 10:03 AM

nothing, In your case it is the correct answer.
But you can create some files: touch apple banana asdwildrty wildness
and check again