Commands using grep (1,935)
-
Diverse trunk and branch, when last index is trunk, show trunk repository name when last index minus one is branches, show branch repository name
0svn info | grep ^URL | awk 'BEGIN {FS="\/"}; {if($(NF-1)=="branches") {print $NF} else if($NF=="trunk") {print $(NF-1)} else {print $NF} } ' -
This will be useful when checking for logs and have to omit specific weblogic or apache server's log information which are redundant and unnecessary. Show Sample Output
0tail -f test | grep -v "bea" -
0vzctl enter `vzlist -a | grep $CONTAINER_IP 2 | awk '{ print $1}'`
-
get the resolution of current desktop settings Show Sample Output
0xwininfo -root | grep 'geometry' | awk '{print $2;}' -
0docker images | awk '{ print $3 }' | grep -v IMAGE | xargs docker rmi
-
0cat [mysql_dump_file] | grep "Table structure" | cut -c 30- | tr '\n' ' ' | rev | cut -c 2- | rev | tr -d '`'
-
Diff 2 branches, for a type of file & having a string in the diff
0git diff t1_clone tlocal4 --name-only | grep -i "swift" | xargs git diff t1_clone tlocal4 --word-diff-regex="NSLocalized" -
-name : base of filename -o : 'or' '*.c' : avoiding "paths must precede expression" error message -type f : only find file type --color: hightlight specific word with color -E : extended regexp Show Sample Output
0find ./$(PATH) -name '*.h' -o -name '*.c' -type f | xargs grep --color -E '*Data*' -
to find and cut between to strings with grep and cut Show Sample Output
0echo '<div class="Btn">link to open </div>' | grep -oP '(?<="Btn").*?(?= </div>)' | cut -d ">" -f2 -
Useful in scripts to compare known malicious IP addresses with what you are actually blocking. Show Sample Output
0ufw status | sort | uniq | grep -E -o "([0-9]{1,3}[\.]){3}[0-9]{1,3}" -
0synclient TouchpadOff=$(synclient -l | grep -q 'TouchpadOff.*1'; echo $?)
-
Show the executable that spawned the process and show the PID and ORACLE_HOME relative to the environment within which the process is running.
0ps -ef | grep [p]mon | awk '{print $2}' | xargs -I {} ps eww {} | awk '{print $1 " " $5 " " $6 " " $0}' | sed 's/\(S*\) \(S*\) .*ORACLE_HOME/\1 \2/g' | cut -f1,2,3 -d" " -
Check the connection of the maximum number of IP Show Sample Output
0netstat -na | grep ESTABLISHED | awk '{print$5}' | awk -F : '{print$1}' | sort | uniq -c | sort -r -
0grep -rnw <directory to search for> -e --include \*.x "your_text"
-
0grep -rnw --include \*.x -e "text" <dir>
-
All the other example fail when running in a folder containing too many files due to * being saturated. This command does not use *, allowing me to run it in one folder containing over 300000 audio files. As to running on so many files, I used GNU parallel in order to spawn as many processes as cores, tremendously fasting up the process. Show Sample Output
0ls|grep ".wav"|parallel -j$(nproc) soxi -D {}|awk '{SUM += $1} END { printf "%d:%d:%d\n",SUM/3600,SUM%3600/60,SUM%60}' -
0if grep ENABLED=yes /etc/ufw/ufw.conf>/dev/null; then echo "enabled"; else echo "disabled"; fi
-
0find . -type f | xargs grep <keyword>
-
Taken from: https://unix.stackexchange.com/questions/129159/record-every-keystroke-and-store-in-a-file Author: Stephane Chazelas Show Sample Output
0xinput list | grep -Po 'id=\K\d+(?=.*slave\s*keyboard)' | xargs -P0 -n1 xinput test -
0processid=$(ps aux | grep 'nginx' | grep -v grep| awk '{print $2}')
-
Continuously watches postgres, showing the instances using the most RAM at the top. Show Sample Output
0watch -n 1 '{ ps aux | head -n 1; ps aux --sort -rss | grep postgres | grep -v grep; } | cat' -
alternative to pidof command Show Sample Output
0processid =$(ps aux | grep 'ProcessName' | grep -v grep| awk '{print $2}') -
0ifconfig | grep "inet addr:" | cut -d: -f2 | awk {'print($1)'} | grep -v 127.0
-
0netstat -tn 2>/dev/null | grep :80 | awk '{print $5}' | cut -d: -f1 | sort | uniq -c | sort -nr | head
-
0grep '^\(default\|smtp\|relay\)[^ ]*concurrency[^ ]*'
- ‹ First < 57 58 59 60 61 > 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 grep