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.

World cup college
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

2010-03-18 - Top 10 commands explained
There's a great article by Peteris Krumins explaining the current top 10 commands: http://www.catonmat.net/blog/top-ten-one-liners-from-commandlinefu-explained/
2010-03-03 - Commandlinefu @ SXSW 2010
Am going to be at SXSW this year, in case you want to submit any CLI nuggets or suggestions to me in person. Ping me on the @codeinthehole Twitter account.
2009-09-12 - Email updates now available
You can now enable email updates to let you know each time you're command is commented on.
2009-07-11 - API and javascript blog widget now available
A simple API has been released, allowing commands to be retrieved in various formats. This also allows commands to be embedded on blogs/homepages.
Hide

Tags

Hide

Functions

nohup that doesn't generate nohup.out

Terminal - nohup that doesn't generate nohup.out
nohup <command> 2> /dev/null > /dev/null &
2009-03-09 16:54:04
User: AmadeusZull
Functions: nohup
1
nohup that doesn't generate nohup.out

I'm sure this can be piped into another way. Please share!

Know a better way?

If you can do better, submit your command here.

What others think

nohup <command> > /dev/null 2>&1&

Explanation here: http://mywiki.wooledge.org/BashFAQ/055

Comment by DEinspanjer 77 weeks and 3 days ago

As DEinspanjer has pointed out, the 2>&1 is a handy shortcut for redirecting the error stream (2) to the same place as the output stream (1). This is also handy if you need to perform an action upon the error output of a command using pipes, e.g. grep --help 2>&1 | sed "s/grep/grape/g". Without the error stream redirect, the grep would fail as help text is typically written to the error stream.

Comment by oniony 77 weeks and 2 days ago

What's wrong with &>?

nohup command &> /dev/null
Comment by atoponce 77 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts