Commands using xargs (769)
-
-3find . -name *.php | xargs grep -i -n 'TERM'
-
Linux : these script enable you to edit multiple files and remove exact phrase from multiple files
-3grep -r "mystring" . |uniq | cut -d: -f1 | xargs sed -i "s/mystring//" -
This will, for an application that has already been removed but had its configuration left behind, purge that configuration from the system. To test it out first, you can remove the last -y, and it will show you what it will purge without actually doing it. I mean it never hurts to check first, "just in case." ;)
-3dpkg-query -l| grep -v "ii " | grep "rc " | awk '{print $2" "}' | tr -d "\n" | xargs aptitude purge -y -
Find and kill multiple instances of a process with one simple command.
-3pgrep rouge-process | xargs sudo kill -9 -
-3ps ux|grep <process name>|awk '{print $2}'|xargs -n 1 kill
-
it recursively searches your project's directories and sum the lines of every source [.c or .h]. Then it gives you the total.
-3find -name *.\[c\|h\] | xargs wc -l -
Original submitter's command spawns a "grep" process for every file found. Mine spawns one grep with a long list of all matching files to search in. Learn xargs, everyone! It's a very powerful and always available tool.
-3find . -name "*.[ch]" -print | xargs grep -i -H "search phrase" -
-3pgrep -u username php5-fcgi | xargs kill -9
-
-3find . -type d -print0 | xargs -0 du -s | sort -n | tail -10 | cut -f2 | xargs -I{} du -sh {} | sort -rn
-
When you do a ls -1 | xargs rm it wouldn't workd because those files have spaces. So you must use find -print0 and xargs -0
-3find /Users/jpn/.ievms/ -type f -print0| xargs -0 du -sh -
After this command you can review doit.sh file before executing it. If it looks good, execute: `. doit.sh`
-3find . | xargs grep -l "FOOBAR" | awk '{print "rm -f "$1}' > doit.sh -
-4accurev stat -M -fl | awk '{print "\"" $0 "\""}' | xargs accurev pop
-
Will search recursively and output the searchResult.txt in the same folder you are located.
-4find . -name "*.php" | xargs egrep -i -s 'specialFunction' > searchresult.txt -
Well this can come handy , when you don't feel like playing with pid rather if you know the process name say "firefox",it would kill it.The script given below would kill the process with its name given as first parameter , though not robust enough to notify that process doesn't exist , well if you know what you are doing that's wouldn't be a problem.:) ---- killhim.sh ---- #!/bin/bash ps -u $USER |grep $1 | awk '{ print $1}'| xargs kill ----
-4ps -u $USER |grep $1 | awk '{ print $1}'| xargs kill -
-4ls | xargs du -sh
-
root@wow/var/spool/clientmqueue # rm spam-* /bin/rm: Argument list too long.
-4find . -name 'spam-*' |xargs rm;find . -name 'spam-*' -print0 | xargs -0 rm -
if Argument list too long
-4echo **/* | xargs grep 'hoge' -
-4/bin/ls *.png | xargs -l1 -I {} convert {} -modulate 100,100,70 ../../icons/32x32/{}
-
# define user pid to kill PID=httpd ; # kill all pids ps aux | grep $PID | grep -v grep | awk '{print $2}' | xargs kill -9 Show Sample Output
-4PID=httpd ; ps aux | grep $PID | grep -v grep | awk '{print $2}' | xargs kill -9 -
Did some research and found the previous command wrong, we don't kill a zombie but its parent. Just made some modifcation to khashmeshab's command.
-4ps -xaw -o state,ppid | grep Z | grep -v PID | awk '{ print $2 }' | xargs kill -9 -
Watches for file modifications in the current directory and tails the file.
-4watch 'ls -tr1 | tail -n1 | xargs tail' -
xargs will automatically determine how namy args are too many and only pass a reasonable number of them at a time. In the example, 500,002 file names were split across 26 instantiations of the command "echo". Show Sample Output
-4ls | xargs WHATEVER_COMMAND -
One liner is based on this article: https://www.computerhope.com/issues/ch001307.htm Show Sample Output
-4lspci|grep -i "VGA Compatible Controller"|cut -d' ' -f1|xargs lspci -v -s|grep ' prefetchable' -
-5ps aux | grep 'httpd ' | awk {'print $2'} | xargs kill -9
-
-5find ./ -mtime -5 | xargs rm -f
- ‹ First < 28 29 30 31 >
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 xargs