I know that the > sign is used for output redirection in the command line, but I'm having trouble finding something that explains the use of 2>&1 in the command line. For example:

curl http://www.google.com > /dev/null 2>&1 &

4 Answers 4


The 1 denotes standard output (stdout). The 2 denotes standard error (stderr).

So 2>&1 says to send standard error to where ever standard output is being redirected as well. Which since it's being sent to /dev/null is akin to ignoring any output at all.

  • 4
    Is there a reason that an ampersand appears before the 1, but not before the 2? I thought the & was a reserved character for running a job in the background, but I guess that's only if the ampersand appears as a long character at the end of a command...? Nov 16, 2009 at 23:24
  • 11
    Because 0 (stdin), 1 (stdout) and 2 (stderr) are actually file descriptors the shell requires an ampersand put in front of them for redirection. It duplicates the file descriptor in this case effectively merging the two streams of information together.
    – Chealion
    Nov 16, 2009 at 23:36
  • 14
    Think of it this way: if you just had "1" with no ampersand, the shell would create a file named "1" and redirect stderr output to it.
    – CarlF
    Nov 17, 2009 at 6:05
  • 1
    Okay, would this alone be valid then? curl http://www.google.com 2>/dev/null How does the command line know that the "2" here is intended to mean stderr and isn't actually the second parameter that I'm passing to the curl command? Nov 17, 2009 at 18:21
  • 1
    @Matt Huggins: Yes. That would send all output from stderr straight to /dev/null instead. You can see it in practice by trying curl, curl 1>/dev/null and curl 2>/dev/null just to see the output change. Again the ampersand is only needed for the file descriptor being redirected to.
    – Chealion
    Nov 18, 2009 at 0:34


Fetch http://www.google.com in the background and discard both the stdout and stderr.

curl http://www.google.com > /dev/null 2>&1 &

is the same as

curl http://www.google.com > /dev/null 2>/dev/null &


0, 1 and 2 represent the standard file descriptors in POSIX operating systems. A file descriptor is a system reference to (basically) a file or socket.

Creating a new file descriptor in C can look something like this:

fd = open("data.dat", O_RDONLY)

Most Unix system commands take some input and output the result to the terminal. curl will fetch whatever is at the specified url (google dot com) and display the result to stdout.

curl result


Like you said < and > are used to redirect the output from a command to somewhere else, like a file.

For example, in ls > myfiles.txt, ls gets the current directory's contents and > redirects its output to myfiles.txt (if the file doesn't exist it is created, otherwise overwritten, but you can use >> instead of > to append to the file instead). If you run the command above, you will notice nothing is displayed to the terminal. That usually means success in Unix systems. To check this cat myfiles.txt to display the file contents to the screen.

> /dev/null 2>&1

The first part > /dev/null redirects the stdout, that is curl's output to /dev/null (more on this ahead) and 2>&1 redirects the stderr to the stdout (which was just redirected to /dev/null so everything will be sent to /dev/null).

The left side of 2>&1 tells you what will be redirected, and the right side tells you where to. The & is used on the right side to distinguish stdout (1) or stderr (2) from files named 1 or 2. So, 2>1 would end up creating a new file (if it doesn't exist already) named 1 and dump the stderr result in there.


/dev/null is an empty file, a mechanism used to discard everything written to it. So, curl http://www.google.com > /dev/null is effectively suppressing curl's output.

> /dev/null

But why is there some stuff still displayed on the terminal?. This is not curl's regular output, but data sent to the stderr, used here for displaying progress and diagnostic information and not just errors.

curl http://www.google.com > /dev/null 2>&1 ignores both curl's output and curls progress information. The result is nothing is displayed on the terminal.


The & at the end is how you tell the shell to run the command as a job in the background. This causes the prompt to return immediately while the command is run asynchronously behind the scenes. To see the current jobs type jobs in your terminal. Note this is different from the processes running in your system. To see those type top in the terminal.


  • 3
    This is one of the best answers on the entire website from a layout perspective, well done!
    – OmarOthman
    Apr 4, 2016 at 14:32
  • One thing I'm not getting is why you would want to send everything to /dev/null ? Don't you want the results of the curl at least somewhere useful?
    – skube
    Nov 15, 2016 at 23:40
  • @skube Right. In this case it's not clear to me why the user wants to discard both stdout and stderr. OP probably just wanted to understand what the syntax meant.
    – j--
    Nov 16, 2016 at 2:17

2 refers to STDERR. 2>&1 will send STDERR to the same location as 1 (STDOUT).


My understand as follow:

If you only want to read the Output and Error information of the command on the screen, then just write: curl http://www.google.com

And some times you want to save the Output information to a file instead of terminal screen for later review, then you can write: curl http://www.google.com > logfile

But in this way, the StdErr information will be omitted, since > only redirect the StdOut to logfile.

So if you care about the error information of the command once it fail to execute, then you need to combine StdOut with StdErr by using 2>&1 (which means fold StdErr into StdOut), so the following command line can be written: curl http://www.google.com > logfile 2>&1

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .