Commands using wc (172)
-
0watch -n0.5 'ps -e -o pid,vsz,comm= | sort -n -k 2 | grep apache | wc -l'
-
count all the lines of code in specific directory recursively in this case only *.php can be *.*
0find . -name '*.php' | xargs wc -l -
Works on AIX, HP-UX, Linux
0find . -name "*.py" -exec wc -l {} \; -
0find -maxdepth 1 -type d | while read dir; do count=$(find "$dir" -regextype posix-extended -iregex '.*\.(jpg|gif|png|jpeg)' | wc -l); echo "$dir ; $count"; done
-
The command outputs the number of commits made to a git repository be leveraging the git-log git command and the wc command that ships with linux coreutil Show Sample Output
0git log --pretty=oneline | wc -l -
This is helpful when approaching a new codebase and wondering where the bulk of the code is located Show Sample Output
0find . -name '*.c*' -o -name '*.h' -exec wc -l {} \; | sort -n | tail -
Count the number of unique colors there are in a websites css folder (136 is way too many imho time to get people stick to a color scheme) Show Sample Output
0grep -r -h -o 'color: #.*' css/*|sort|uniq -c|sort -n|wc -l -
Uses git grep for speed, relies on a valid she-bang, ignores leading whitespace when stripping comments and blank lines Show Sample Output
0egrep -v '^\s*($|#)' $(git grep -l '#!/bin/.*sh' *) | wc -l -
Show file count into directories. Usefull when you try to find hugh directories that elevate system CPU (vmstat -> sy) Show Sample Output
0find / -type d | while read i; do ls $i | wc -l | tr -d \\n; echo " -> $i"; done | sort -n -
netstat doesn't always function similarly across the board. Also the use of three commands in the original (netstat followed by grep followed by grep) is a waste of pipes
0lsof -i :80 | tee /dev/stderr | wc -l -
So simple
0find . -type f | xargs wc -l -
I wanted to count and display the top directories containing JavaScript files in some of my project. Here it is. Maybe it can be written to more simply syntax by using find -exec...
0for f in `find . -type d`; do pushd . > /dev/null ; echo -e `cd $f ; find . -name \*\.js | wc -l` "\t" $f | grep -v ^0 ; popd >/dev/null; done | sort -n -k 1 -r | less -
0find . -mindepth 2 -name "*.js" -type f |wc -l
-
On Linux, use watch -n 1 ls path/to/dir H/t: https://stackoverflow.com/a/9574123/805405 Show Sample Output
0while :; do clear; ls path/to/dir | wc -l; sleep 1; done -
I needed to get a feel for how "old" different websites were, based on their directories. Show Sample Output
-1date -d "@$(find dir -type f -printf '%C@\n' | sort -n | sed -n "$(($(find dir -type f | wc -l)/2))p")" +%F -
-1lsof -p <process_id> | wc -l
-
Have wc work on each file then add up the total with awk; get a 43% speed increase on RHEL over using "-exec cat|wc -l" and a 67% increase on my Ubuntu laptop (this is with 10MB of data in 767 files).
-1find . -type f -name '*.c' -exec wc -l {} \; | awk '{sum+=$1} END {print sum}' -
If you have a folder with thousand of files and want to have many folder with only 100 file per folder, run this. It will create 0/,1/ etc and put 100 file inside each one. But find will return true even if it don't find anything ... Show Sample Output
-1folder=0;mkdir $folder; while find -maxdepth 1 -type f -exec mv "{}" $folder \; -quit ; do if [ $( ls $folder | wc -l ) -ge 100 ]; then folder=$(( $folder + 1 )); mkdir $folder; fi ; done -
Returns the number of running httpd processes Show Sample Output
-1pidof httpd | wc -w -
-1wc -L files
-
-1cat /etc/passwd | wc -l
-
-1for f in ~/.mcabber/histo/*; do a=`egrep "^(MR|MS)" $f | wc -l`; echo $f: $a | awk -F\/ '{print $6}'; done
-
There's nothing particularly novel about this combination of find, grep, and wc, I'm just putting it here in case I want it again. Show Sample Output
-1find . -name '*.java' -o -name '*.xml' | grep -v '\.svn' | xargs wc -l -
-1who am i | wc -l
-
-1grep -o 'pattern' | wc -l
- ‹ First < 4 5 6 7 >
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 wc