By default find "goes down into" (recurses) subdirectories, so simply telling you that the file exists (using a return code ) is pointless. find may locate several files in several directories with the same name, it may find one or none. But without knowing the FULL NAME (directory/filename) of the file the fact that the file exists somewhere is completely useless without actual name of the file.
So error return codes are mostly limited to errors involving access/existence of directories, or other standard filesystem-related problems like too many symbolic links.
[lyang0@ala lyang0]$ mkdir test
[lyang0@ala lyang0]$ cd test/
[lyang0@ala test]$ find ./ -name xx;echo $?
0
Correct and no error!
What does 0 mean? That the execution of find was successfull - Has nothing to do with finding something - what we are trying to tell you from the beginning: Dont mix up what an exit code is for...
In other words if you want to use if you will have to check the output of find...
Quote:
I mean can we use "if" in the bash to judge if it find or not
1)to use "if" to judge it find
2)to use if to judge it not find
I dont understand here... either 1) or 2) ...
You use if for a condition ( boolean ), the possible output of find is not a boolean so like that (brut de fonderie as we would say in french...) you cannot but will have to use the output in a way you get a yes/no type of answer e.g. Is there an output ( and so find found something...) or is there more than 0 found... look at my previous posts
From now you have enough to be able to sort yourself out...
Last edited by vbe; 07-10-2012 at 01:05 PM..
Reason: typos
[lyang0@ala lyang0]$ mkdir test
[lyang0@ala lyang0]$ cd test/
[lyang0@ala test]$ find ./ -name xx;echo $?
0
Correct and no error!
What does 0 mean? That the execution of find was successfull - Has nothing to do with finding something - what we are trying to tell you from the beginning: Dont mix up what an exit code is for...
I can use
Code:
if grep "xxx" * -r;then
echo "found"
else
echo "not found"
fi
[
The quesion how can I use "find" like "grep", you know whether find or not with find it always "1"
In general it always helps if you post what Operating System and version you have and what Shell you use. There is variation in the find command and in my solution there may be code which doesn't work on your system.
Question 1)
One method is to use a workfile:
Code:
my_workfile=/tmp/my_workfile.$$
find bin/ -xdev -type f -name 'bla.c' -print > ${workfile}
# Anything in the file?
if [ -s ${workfile} ]
then
echo "Files found were"
cat ${workfile}
else
echo "No files found"
fi
Note the use of -type f and -xdev and the quotes round the name of the file.
I've assumed that bin/ is some directory under your home directory. On most systems /bin is a link to /usr/bin anyway.
Question 2)
Easier with two finds:
Code:
my_workfile=/tmp/my_workfile.$$
find bin/ -xdev -type f -name 'bla.c' -print > ${workfile}
find /usr/bin/ -xdev -type f -name 'bla.c' -print >> ${workfile}
# Anything in the file?
if [ -s ${workfile} ]
then
echo "Files found were"
cat ${workfile}
else
echo "No files found"
fi
Question 3)
It is preferable to specify a positive list of mountpoints or directories you want to search rather than to build a complex find -prune. On some systems you will never want to search certain filesystems like /proc or /tmp.
Last edited by methyl; 07-10-2012 at 01:56 PM..
Reason: typos
Hello,
This is a bit complicated for me.
My scenario in MyFile:
Search string1,
When string1 is found, grep the line containing string1, go back over that line in upward direction and grep the first line containing string2.
Here is an example:
MyFile
His email address... (17 Replies)
I need assistance with following requirement, I am new to Unix.
I want to do the following task but stuck with file creation date(sysdate)
Following is the requirement
I need to create a script that will read the abc/xyz/klm folder and look for *.err files for that day’s date and then send an... (4 Replies)
Hi Friends,
Please help me to sort out this problem, I am running this in centos o/s and whenever I run this script I am getting "find: missing argument to `-exec' " but when I run the same code in the command line I didn't find any problem. I am using perl script to run this ... (2 Replies)
Hi all ,
I'm new to unix
I have a checked project , there exists a file called xxx.config .
now my task is to find all the files in the checked out project which references to this xxx.config file.
how do i use grep or find command . (2 Replies)
Hello everyone,
first post here, trying to learn scripting on my own and this forum as been really helpful so far. I made few little scripts working great but I m facing some problems with RE.
I have a bunch of files in many subdirectories called *001.ext *002.ext OR simple *.ext or *01.ext... (7 Replies)
I need to find whether there is a file named vijay is there or not in folder named "opt" .I tried "ls *|grep vijay" but it showed permission problem.
so i need to use find command (6 Replies)
Yes , I have to find a file in unix without using any find or where commands.Any pointers for the same would be very helpful as i am beginner in shell scritping and need a solution for the same.
Thanks in advance.
Regards
Jatin Jain (10 Replies)
Hello,
I create a file touch 1201093003 fichcomp
and inside a repertory (which hava a lot of files) I want to list all files created before this file :
find *.* \! -maxdepth 1 - newer fichcomp but this command returned bash: /usr/bin/find: Argument list too long
but i make a filter all... (1 Reply)
