nohup that doesn't generate nohup.out

nohup <command> 2> /dev/null > /dev/null &
I'm sure this can be piped into another way. Please share!

2
2009-03-09 16:54:04

What Others Think

nohup <command> > /dev/null 2>&1& Explanation here: http://mywiki.wooledge.org/BashFAQ/055
DEinspanjer · 501 weeks and 4 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.
oniony · 501 weeks and 4 days ago
What's wrong with &>? nohup command &> /dev/null
atoponce · 501 weeks and 3 days ago

What do you think?

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.

What's this?

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.

Share Your Commands



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: