Commands using grep (1,935)
-
search_criteria = what do you want to kill pid = pid of you dont kill
-6kill -9 `ps aux | grep "search_criteria" | awk '{if ($2 != pid) print $2}'` -
replace apt-get with your distro's package manager. Where 'something' is the package name, and 'specific' is what you're specifically looking for. This helps if your query is 2+ words long. Show Sample Output
-6apt-get search something | grep specific -
Removed unneeded grep -v by making the initial grep unable to match itself.
-6ps -ef | grep [j]boss | awk '{print $2}'|xargs kill -9 -
-6lwp-dump http://www.boredomsoft.org/ip.php|grep Client
-
get the ip address on your LAN Show Sample Output
-6ifconfig |grep broadcast | awk '{print $2}' -
Go to "https://twitter.com/search/realtime?q=%23TeamFollowBack&src=hash" and then copy al the text on the page. If you scroll down the page will be bigger. Then put al the text in a text file called twit.txt If you follow the user there is a high probability the users give you follow back. To follow all the users you can use an iMacros script.
-6for a in $(seq 5 8); do cat twit.txt | cut -d " " -f$a | grep "^@" | sort -u; done > followlst.txt -
-6grep -A 3 -i "example" demo_text
-
-6ps -ef | grep PROCESS | grep -v grep | awk '{system "kill -9" $2}
-
This decompresses the file and sends the output to STDOUT so it can be grepped. A good one to put in loops for searching directories of gzipped files, such as man pages. Show Sample Output
-7zcat /usr/share/man/man1/grep.1.gz | grep "color" -
This is a nice way to kill processes.. the example here is for firefox!!! substitute firefox for whatever the process name is... Show Sample Output
-7ps aux | grep -i firefox | grep -v grep | awk '{print $2}' | xargs -t -i kill -9 {} -
-7ps auxwww | grep outofcontrolprocess | awk '{print $9}' | xargs kill -9
-
This command kills all processes with 'SomeCommand' in the process name. There are other more elegant ways to extract the process names from ps but they are hard to remember and not portable across platforms. Use this command with caution as you could accidentally kill other matching processes! xargs is particularly handy in this case because it makes it easy to feed the process IDs to kill and it also ensures that you don't try to feed too many PIDs to kill at once and overflow the command-line buffer. Note that if you are attempting to kill many thousands of runaway processes at once you should use 'kill -9'. Otherwise the system will try to bring each process into memory before killing it and you could run out of memory. Typically when you want to kill many processes at once it is because you are already in a low memory situation so if you don't 'kill -9' you will make things worse
-7ps axww | grep SomeCommand | awk '{ print $1 }' | xargs kill -
You need curl.. and a Mac of course.
-7curl -s -u user:password http://twitter.com/statuses/friends_timeline.rss | grep title | sed -ne 's/<\/*title>//gp' | head -n 4 | say -v Bruce -
-7grep -v ^# file.conf | grep -v ^$ > new_file.conf
-
Work only with bash and apt-file installed. When it found an unknow command, it will search for a file named "scribus" (in my example), in a folder named bin and then install the corresponding package. After installation, it will run the command. Usefull juste after reinstalling linux and missing lot of package. Show Sample Output
-7function command_not_found_handle(){ apt-get install $( apt-file search "$1" | grep bin | grep -w "$1" | head -n1 | cut -d ':' -f 1 ) && $* ; } -
-8#!/bin/sh for dir in `ls -A | grep -v .sh`; do chown -R $dir:$dir $dir done
-
-8ls -RAx | grep "svn:$" | sed -e "s/svn:/svn/" | xargs rm -fr
-
-8for i in $(file * | grep broken | cut -d : -f 1); do rm $i; done
-
Remove all zero size files from current directory. Its a not recursive option like: find . -size 0c -exec rm {} \;
-8ls -s|grep -E "^ *0"|sed "s/^ *0 //g"|xargs -i rm "{}" -
After seeing the command you wish to repeat, just invoke it using the ! syntax.
-9history | grep ssh -
Will find all files containing "sample" in the current directory and in the directories below.
-9find . -exec grep -l "sample" {} \; -
-9find . -type l | xargs file | grep broken
-
I know how hard it is to find an old command running through all the files because you couldn't remember for your life what it was. Heres the solution!! Grep the history for it. depending on how old the command you can head or tail or if you wanted to search all because you cannot think how long ago it was then miss out the middle part of the command. This is a very easy and effective way to find that command you are looking for.
-9cat .bash_history | tail -100 | grep {command} -
recently some in the #linux shared this. to find out the kernel version name from the binary without using uname Show Sample Output
-10strings /boot/kernel-file | grep 2.6 -
gunzip all .gz file in current dir
-10ls | grep .gz >> list.txt && cat list.txt | while read x ; do gunzip -d $x ; done && rm -rf list.txt - ‹ First < 75 76 77 78 >
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