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

Close shell keeping all subprocess running

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

Alternatives

There is 1 alternative - vote for the best!

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

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
3

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

Use

disown -a && exit

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

Comment by DNSpyder 262 weeks and 5 days ago

This is an excellent idea.

Comment by haivu 262 weeks and 5 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 261 weeks and 6 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 261 weeks and 5 days ago

@amosshapira:

man bash | grep -A9 "disown \["
Comment by quodlibetor 261 weeks and 5 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 261 weeks and 5 days ago

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

Comment by vutcovici 222 weeks and 2 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 48 weeks ago

Your point of view

You must be signed in to comment.

Related sites and podcasts