Hide

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.

Hide

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:

Hide

News

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.
Hide

Tags

Hide

Functions

Find out how much data is waiting to be written to disk

Terminal - Find out how much data is waiting to be written to disk
grep ^Dirty /proc/meminfo
2011-08-24 08:48:49
User: h3xx
Functions: grep
30
Find out how much data is waiting to be written to disk

Ever ask yourself "How much data would be lost if I pressed the reset button?"

Scary, isn't it?

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

good!

Comment by davidpgero 139 weeks and 1 day ago

grep ^Dirty /*/meminfo # works on my system

#but ls /*/meminfo or eacho /*/meminfo only show a single file on my system.

Comment by Jessehz 139 weeks and 1 day ago

grep ^Dirt /*/m*i* #may not work on other systems

#I'm running Ubuntu 11.04 AMD64

Comment by Jessehz 139 weeks and 1 day ago

Stupid.

Comment by RanyAlbeg 139 weeks and 1 day ago

@RanyAlbeq: You just wish you'd thought of it.

Comment by h3xx 139 weeks and 1 day ago

@h3xx lol. Well said.

Comment by DaveQB 139 weeks and 1 day ago

To salve your conscience use

sync

to write back data manually...

Comment by hons 138 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts