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.

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Close shell keeping all subprocess running

Terminal - Close shell keeping all subprocess running
disown -a && exit
2009-04-10 12:22:34
User: prayer
Close shell keeping all subprocess running


There are 2 alternatives - vote for the best!

Terminal - Alternatives
^Z $bg $disown
2009-03-17 21:52:52
User: fall0ut

You're running a script, command, whatever.. You don't expect it to take long, now 5pm has rolled around and you're ready to go home... Wait, it's still running... You forgot to nohup it before running it... Suspend it, send it to the background, then disown it... The ouput wont go anywhere, but at least the command will still run...

^z; bg; disown
2011-12-06 20:48:01
User: anarcat

background and disown, but with a proper one-line syntax

Know a better way?

If you can do better, submit your command here.

What others think


disown -a && exit

to ensure that the shell will stay open if not all childs have been successfuly disowned.

Comment by DNSpyder 393 weeks and 3 days ago

This is an excellent idea.

Comment by haivu 393 weeks and 3 days ago

Thanks. I have often thought that commands run without http://www.commandlinefu.com/commands/using/nohup">nohup or http://www.commandlinefu.com/commands/tagged/52/screen">screen required babysitting.

Comment by mark_stafford 392 weeks and 4 days ago

which shell is it in (I assume this is a shell built in)?

I can't find it on ubuntu/bash.

Comment by amosshapira 392 weeks and 3 days ago


man bash | grep -A9 "disown \["
Comment by quodlibetor 392 weeks and 3 days ago

Awesome. I hate nohupping my virtualbox startup, because the output goes to nohup.out and I have to check the file to make sure it actually started. Disowning instead:

VBoxHeadless -startvm debian &

[1] 1414

VirtualBox Headless Interface 2.1.2

(C) 2008-2009 Sun Microsystems, Inc.

All rights reserved.

Listening on port 3389

disown %1 jobs
Comment by sud0er 392 weeks and 3 days ago

it is a shell (bash, zsh...) built-in.

Comment by vutcovici 352 weeks and 6 days ago

i have a question, if you ran a command without an '&' appended, then can the command

disown -a && exit

make sense?

in this case, i often "^z" first, then "bg" put the command to the backgroud, at last, run "disown -a".

Comment by byrgl5 178 weeks and 5 days ago

Your point of view

You must be signed in to comment.