Professional Documents
Culture Documents
Scala Cookbook
By Alvin Alexander
Learn more
categories
1
find, which makes find even more
powerful.
2
find /opt /usr /var -name foo.scala -type f # search mult
case-insensitive searching
--------------------------
find . -iname foo # find foo, F
find . -iname foo -type d # same thing,
find . -iname foo -type f # same thing,
3
find files by modification time
-------------------------------
find . -mtime 1 # 24 hours
find . -mtime -7 # last 7 days
find . -mtime -7 -type f # just files
find . -mtime -7 -type d # just dirs
On a related note, dont forget the locate command. It keeps a database on your
Unix/Linux system to help find files very fast:
locate command
--------------
locate tomcat.sh # search the entire filesystem for 'tomcat.sh' (uses the loca
locate -i spring.jar # case-insensitive search
4
If you know of any more good find commands to share, please leave a note in the
Comments section below.
The remaining sections on this page describe more fully the commands just shown.
This first Linux find example searches through the root filesystem ("/") for the file
named Chapter1. If it finds the file, it prints the location to the screen.
On Linux systems and modern Unix system you no longer need the -print option at
the end of the find command, so you can issue it like this:
The -type f option here tells the find command to return only files. If you dont use it,
the find command will returns files, directories, and other things like named pipes and
device files that match the name pattern you specify. If you don't care about that, just
leave the -type f option off your command.
This next find command searches through only the /usr and /home directories for any
file named Chapter1.txt:
To search in the current directory and all subdirectories just use the . character to
reference the current directory in your find commands, like this:
This next example searches through the /usr directory for all files that begin with the
letters Chapter, followed by anything else. The filename can end with any other
5
combination of characters. It will match filenames such as Chapter, Chapter1,
Chapter1.bad, Chapter-in-life, etc.:
This next command searches through the /usr/local directory for files that end with the
extension .html. These file locations are then printed to the screen:
Every option you just saw for finding files can also be used on directories. Just replace
the -f option with a -d option. For instance, to find all directories named build under
the current directory, use this command:
To find all files that don't match a filename pattern, use the -not argument of the find
command, like this:
That generates a list of all files beneath the current directory whose filename DOES
NOT end in .html, so it matches files like *.txt, *.jpg, and so on.
You can combine the Linux find and grep commands to powerfully search for text
6
strings in many files.
This next command shows how to find all files beneath the current directory that end
with the extension .java, and contain the characters StringBuffer. The -l
argument to the grep command tells it to just print the name of the file where a match
is found, instead of printing all the matches themselves:
(Those last few characters are required any time you want to exec a command on the
files that are found. I find it helpful to think of them as a placeholder for each file that is
found.)
This next example is similar, but here I use the -i argument to the grep command,
telling it to ignore the case of the characters string, so it will find files that contain
string, String, STRING, etc.:
This command searches through the /usr/local directory for files that end with the
extension .html. When these files are found, their permission is changed to mode 644
(rw-r--r--).
This find command searches through the htdocs and cgi-bin directories for files that
end with the extension .cgi. When these files are found, their permission is changed to
mode 755 (rwxr-xr-x). This example shows that the find command can easily search
through multiple sub-directories (htdocs, cgi-bin) at one time:
7
From time to time I run the find command with the ls command so I can get detailed
information about files the find command locates. To get started, this find command
will find all the *.pl files (Perl files) beneath the current directory:
./news/newsbot/old/3filter.pl
./news/newsbot/tokenParser.pl
./news/robonews/makeListOfNewsURLs.pl
That's nice, but what if I want to see the last modification time of these files, or their
filesize? No problem, I just add the ls -ld command to my find command, like this:
The "-l" flag of the ls command tells ls to give me a "long listing" of each file, while the
-d flag is extremely useful in this case; it tells ls to give me the same output for a
directory. Normally if you use the ls command on a directory, ls will list the contents of
the directory, but if you use the -d option, you'll get one line of information, as shown
above.
Be very careful with these next two commands. If you type them in wrong, or make the
8
wrong assumptions about what you're searching for, you can delete a lot of files very
fast. Make sure you have backups and all that, you have been warned.
Here's how to find all files beneath the current directory that begin with the letters 'Foo'
and delete them.
This one is even more dangerous. It finds all directories named CVS, and deletes them
and their contents. Just like the previous command, be very careful with this command,
it is dangerous(!), and not recommended for newbies, or if you don't have a backup.
The syntax to find multiple filename extensions with one command looks like this:
Just keep adding more "-o" (or) options for each filename extension. Here's a link to
To perform a case-insensitive search with the Unix/Linux find command, use the
-iname option instead of -name. For example, if you want to search for all files and
directories named foo, FOO, or any other combination of uppercase and lowercase
characters beneath the current directory, use this command:
9
find . -iname foo -type d
To find all files and directories that have been modified in the last seven days, use this
find command:
find . -mtime -7
To limit the output to just files, add the -type f option as shown earlier:
If youre just looking for a file by name, and you want to be able to find that file even
faster than you can with the find command, take a look at the Linux locate command.
The locate command keeps filenames in a database, and can find them very fast.
For more details on the find command, check out our online version of the find man
page.
Also, if you have any favorite Linux and Unix find commands youd like to share, please
use the comment form below.
10
related
whats new
11
Submitted by Anonymous (not verified) on September 12, 2009 - 8:27am
I just had a problem with a Bugzilla installation (on an intranet), and finally gave
up on trying to fix all the permission problems, and just made all the bugzilla
subdirectories 775 like this:
12
Submitted by on September 15, 2009 - 10:51am
I've always been lazy in this situation and done something as follows. First, create a
list of all the files you want to remove, putting that list into a file:
But a quick warning: I haven't tested that for syntax errors, but I think it's right.
EXAMPLES
Find files named core in or below the directory /tmp and delete them.
Note that this will work incorrectly if there are any filenames containing
newlines or spaces.
Find files named core in or below the directory /tmp and delete them,
processing filenames in such a way that file or directory names containing
spaces or new-lines are correctly handled.
13
No matter, which approach, be careful, and try a test first (maybe using the echo
command) to make sure it works was expected..
I'll add a new section to this article with this update, but to perform a
case-insensitive search, use the -iname option instead of -name. So, to search for
all files and directories named foo, FOO, or any other combination of uppercase
and lowercase characters beneath the current directory, use this command:
14
find . -type d -name "[A-Z]*"
The -type d option tells find to just look for directories, and the wildcard pattern
"[A-Z]*" says "Search for any directory whose name contains one or more
uppercase characters."
good one!!!
15
Was very helpful. Straight to the point.
16
Is there any way to set a "-quiet" type flag to ignore all the error lines? I get more
"Permission denied" lines than I do results to my find query. I don't see anything in
the man page. I thought maybe I could run the output through grep -v "Permission
denied" but that fails to work.
Often I'd like to know exactly WHERE the files that get found reside. the -print
(default) command only gives the file name. The -ls flag prints out a bunch of data,
including size and full path. You can then use sed/awk (if you know how - I suck at
this too) to pull out specific data from what find returns.
Another cool thing to do is run your find output through wc -l to count all the found
files. e.g.:
find ~music -type f -iname *.mp3 | wc -l
will count all the mp3 files in the music user's home and subdirs.
There is a -[no]warn flag, though I've never used it. The problem with using grep in
this case is that the errors are probably coming out of find on the STDERR stream
instead of STDOUT, so you'll need to get rid of them something like this:
17
find ...your options here... 2> /dev/null
If you haven't used it before, the "2>" symbol lets you redirect STDERR output.
Cheers.
Thanks, you're right, I totally forgot to include an "ls" example. I'll try to add one
here this morning. Usually I use ls with the -ld option, like this:
Simply ultimate..quite impressed by the way you present the usage of the
command. Well done.
18
Submitted by Anonymous (not verified) on November 15, 2010 - 11:36am
Thanks :)
Can someone help me in find files with multiple extensions like .sh or .c or .txt
for ex-
find . -name "*.(c|sh|txt)"
19
Submitted by on January 4, 2011 - 12:34pm
The syntax to find multiple filename extensions with one command looks like this:
Just keep adding more "-o" (or) options for each filename extension. Here's a link
to .
Hi
Can anyone help me to find a directory using "find command" and list the contents
of that directory using ls command.
Eg. Suppose say I want to find the directory called "mosra" in the present workign
directory. This directory may be present anywhere in the path and I want to list
ONLY the directories present in that "mosra" directory.
/nfs/iind/home/sshirnix/public/scripts/perl_scripts
20
Working Dir $ find ./ -name mosra -type d
./aging/hspice/mosra
However ... a problem with that command is that it's like issuing this command
from the directory above the mosra directory:
ls mosra
That command will list all of the files in the mosra folder, which is probably what
you're seeing. To eliminate the output of those filenames, add the -d flag to your ls
command:
21
However, at this point, unless you want more detailed information about the
mosra folder, such as an ls -l command, there's no point in using ls; just use
this command:
(If you're on an older Unix system you may also need the -print argument.)
Hello Alvin,
Thank you very much for the reply and for yor time.
I am grateful to you for your reply.
The command:
find . -name mosra -type d -exec ls {} \;
lists all the directories and files in mosra directory found. However I want to list
ONLY the directories that are present in the mosra directory once it is found.
The command:
find . -name mosra -type d -exec ls -d {} \;
gives the relative path of the mosra directory not the contents in mosra directory.
In fact I want only the directories present in the mosra not the files.
Basically I want the directories present in mosra after finding it in the current path.
Sudhakar
22
Submitted by on March 1, 2013 - 8:53am
Depending on your exact needs you may want to do that in a couple of lines in a
shell script, but you can also get a listing of all directories under the mosra
directory by executing one find command inside the other, like this:
The content of this field is kept private and will not be shown publicly.
Homepage
Subject
Comment
23
Allowed HTML tags: <em> <strong> <cite> <code> <ul type> <ol start type> <li> About text formats
<pre>
Lines and paragraphs break automatically.
Links:
front page me on twitter search privacy
java
java applets
java faqs
misc content
java source code
test projects
lejos
Perl
perl faqs
programs
perl recipes
perl tutorials
Unix
man (help) pages
unix by example
tutorials
source code
24
warehouse
java examples
drupal examples
misc
privacy policy
terms & conditions
subscribe
unsubscribe
wincvs tutorial
function point
analysis (fpa)
fpa tutorial
Other
mobile website
rss feed
my photos
life in alaska
how i sold my business
living in talkeetna, alaska
my bookmarks
inspirational quotes
source code snippets
25