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... Show Sample Output
background and disown, but with a proper one-line syntax
Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?
You must be signed in to comment.
commandlinefu.com is the place to record those command-line gems that you return to again and again. 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.
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
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:
disown -a && exit
to ensure that the shell will stay open if not all childs have been successfuly disowned.man bash | grep -A9 "disown \["
VBoxHeadless -startvm debian &
[1] 1414 VirtualBox Headless Interface 2.1.2 (C) 2008-2009 Sun Microsystems, Inc. All rights reserved. Listening on port 3389disown %1
jobs
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".