What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.

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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.

Top Tags



Chrome sucks

Terminal - Chrome sucks
ps -e -m -o user,pid,args,%mem,rss | grep Chrome | perl -ne 'print "$1\n" if / (\d+)$/' | ( x=0;while read line; do (( x += $line )); done; echo $((x/1024)) );
2013-05-07 22:50:44
Functions: echo grep perl ps read
Chrome sucks

How much memory is chrome sucking?


There is 1 alternative - vote for the best!

Terminal - Alternatives
ps aux | awk '/chrome/ {s+=$6}END{print s/1024}';
2013-05-09 02:30:44
User: DaSheep
Functions: awk ps
ps -o rss= -C Chrome | (x=0; while read rss; do ((x+=$rss)); done; echo $((x/1024)))
ps -A -o rss,command | grep [C]hrome | awk '{sum+=$1} END {printf("%sMB\n",sum/1024)}'
2013-05-08 13:30:59
User: seanubis
Functions: awk grep ps
Tags: grep chrome

Know a better way?

If you can do better, submit your command here.

What others think

Not accurate. This command adds the RSS for each process, but in reality there is much overlap since chrome uses fork. Think of a Venn diagram - this command adds the area of each circle, but this counts the overlap multiple times. To see chrome's memory consumption, just enter the address "about:memory". Also, on my box the grep doesn't work because the process is "chrome" not "Chrome" (fixed by giving grep the "-i" option).

Comment by dstahlke 102 weeks and 4 days ago

awk power ;)

ps aux | awk '/chrome/ {m+=$6}END{print m/1024}';
Comment by DaSheep 102 weeks and 3 days ago

These are both incorrect. They both have very different output but I don't have chrome running!

Comment by techie 102 weeks and 2 days ago

Your point of view

You must be signed in to comment.