Commands using find (1,252)
-
Just search the root of the file hierarchy for matches for a text string. Send errors to a file rather than stdout.
0find / -name '*android*' 2>errors.txt -
you can find all "trace" phrases within everywhere else under the pentest directory.. Show Sample Output
0find /pentest/ -type f -iname "*trace*" -
you can find a special things(with defined -iname "*sql*") from in most of one direcroty(for example from both /etc/ and /pentest/) and then you can want to grep only include "map" word Show Sample Output
0find /etc/ /pentest/ -type f -iname "*sql*" | grep map -
This command does a basic find with size. It also improves the printout given (more clearer then default) Adjusting the ./ will alter the path. Adjusting the "-size +100000k" will specify the size to search for. Show Sample Output
0find ./ -type f -size +100000k -exec ls -lh {} \; 2>/dev/null| awk '{ print $8 " : " $5}' -
I use this find command example to find out all the executable files you can modify it to find readonly file as well.
0find . -perm 777 ?print -
Find is used to "find" all filenames - grep shows those that are invalid.
0find . | grep -E "(\||\\|\?|\*|<|\"|:|>|\+|\[|\])" -
Find all files under "." that are invalid NTFS filenames. Find locates all files, and grep shows the invalid ones.
0find . | grep -E "(\||\\|\?|\*|<|\"|:|>)" -
You must have the android sdk installed with 'adb' executable on your system. This is just a way to loop over files in a folder using 'find' to locate and install android apps. Show Sample Output
0find ~/path/to/apk/files -name '*.apk' -exec adb install {} \; -
0find . -size +10240k -exec stat -c%s" "%n {} \; | sort -rn
-
0sudo find . -name "syslog*.gz" -type f | xargs gzip -cd | grep "Mounted"
-
This let me find some a set of modifications that were made to a rather large tree of files, where the file-names themselves were not unique (actually: insanely redundant and useless. "1.dat 2.dat ..."). Pruning down to last-branch brough things back to the "project-name" scope, and it's then easy to see which branches of the tree have recently changed, or any other similar search. Ideally, it should sort the directories by the mtime of the most recent *file* *inside* the directory, but that's probably outside the scope of a (sane...) command line.
0ls -ltr --directory $(find . -regex "./.*[^/]*\'" -type f | xargs -n 1 dirname | sort | uniq) -
0find -L / -samefile path/to/foo.txt
-
0find / -lname path/to/foo.txt
-
This can be used to delete or archive old mails. In fact, for archiving its a bit different, you need to archive mails with any tools (e.g archivemail), and then deleting (if you want!). Here we use -path ".*/cur/*" to avoid files limit in bash globbing and to search in any inbox (e.g .mymail .spam .whatever). ! -newermt "1 week ago" can be read: All files which is older than "1 week ago", adapt it in consequence. Show Sample Output
0find . -path ".*/cur/*" -type f ! -newermt "1 week ago" -delete -
This command removes *.lock or files from a folder.
0find -name *.lock |xargs rm -f -
Remove all the hidden CVS merge helper files that I keep seeing in my IntellIj project
0find . -name ".#*" -exec rm {} \; -
Improvement on Coderjoe's Solution. Gets rid of grep and cut (and implements them in awk) and specifies some different mplayer options that speed things up a bit. Show Sample Output
0find /path/to/dir -iname "*.ext" -print0 | xargs -0 mplayer -really-quiet -cache 64 -vo dummy -ao dummy -identify 2>/dev/null | awk '/ID_LENGTH/{gsub(/ID_LENGTH=/,"")}{SUM += $1}END{ printf "%02d:%02d:%02d\n",SUM/3600,SUM%3600/60,SUM%60}' -
Helps to fix permissions when a user clobbers them in their home directory or elsewhere. Does not rely on file extension, but uses the `file` command for context.
0find . -type f ! -perm /u+x -printf "\"%p\"\n" | xargs file | grep -i executable -
0sudo find foldername -type d -exec chmod 755 {} ";"
-
0sudo find foldername -type f -exec chmod 644 {} ";"
-
This command finds all files in a folder recursively and sets owner and group to read and write. Leaves all dirs intact. This command does takes care of file names with spaces as well.
0find . -type f -print0 | xargs -0 chmod -v gu=rw -
0find . -type f -name "*.*" -exec cat {} > totalLines 2> /dev/null \; && wc -l totalLines && rm totalLines
-
0find / -name 'tofind.sh' 2>/dev/null
-
the
find -printf "%f\n" prints just the file name from the given path. This means directory paths which contain extensions will not be considered.Show Sample Output0find /some/path -type f -and -printf "%f\n" | egrep -io '\.[^.]*$' | sort | uniq -c | sort -rn -
0find . -type f -print0 | xargs -0 -n1 md5sum | sort -k 1,32 | uniq -w 32 -d --all-repeated=separate | sed -e 's/^[0-9a-f]*\ *//;'
- ‹ First < 27 28 29 30 31 > Last ›
What's this?
commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
Check These Out
Stay in the loop…
- Follow the Tweets.
-
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10 - Subscribe to the feeds.
-
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
- » all commands
- » commands with 3 up-votes (commandlinefu3)
- » commands with 10 up-votes (commandlinefu10)
- » commands using find