What does this mean Dev null 2 >& 1?

/dev/null in Linux is a null device file. This will discard anything written to it, and will return EOF on reading.

This is a command-line hack that acts as a vacuum, that sucks anything thrown to it.

Let’s take a look at understanding what it means, and what we can do with this file.

/dev/null Properties

This will return an End of File (EOF) character if you try to read it using the cat command.

This is a valid file, which can be verified using

This gives me an output of

This shows that this file has a size of 0 bytes, has zero blocks allocated to it. The file permissions are also set that anyone can read/write to it, but cannot execute it.

Since it is not an executable file, we cannot use piping using | operator to redirect to /dev/null. The only way is to use file redirections (>, >>, or <, <<).

The below diagram shows that /dev/null is indeed a valid file.

Let’s now take a look at some common use cases for /dev/null.

Redirection to /dev/null in Linux

We can discard any output of a script that we use by redirecting to /dev/null.

For example, we can try discarding echo messages using this trick.

You will not get any output since it is discarded!

Let’s try running a command incorrectly and pipe it’s output to /dev/null.

We still get an output like this:

Why is this happening? This is because the error messages are coming from stderr, but we are only discarding output from stdout.

We need to take stderr into account as well.

Discard error messages

Let us redirect the stderr to /dev/null, along with stdout. We can use the file descriptor for stderr(=2) for this.

This will give us what we need!

There is another way of doing the same; by redirecting stderr to stdout first, and then redirect stdout to /dev/null.

The syntax for this will be:

Notice the 2>&1 at the end. We redirect stderr(2) to stdout(1). We use &1 to mention to the shell that the destination file is a file descriptor and not a file name.

So if we use 2>1, we will only redirect stderr to a file called 1. This is not what we want!

Conclusion

Hopefully, this clears things up a bit, so that you can now use /dev/null in Linux, knowing what it means! Feel free to ask questions in the comment section below.

References

• StackOverflow Question

Can someone explain to me what is the meaning of "2>&1" doing here in the below cron job

asked Aug 16, 2021 at 5:06

mahen3dmahen3d

3,90512 gold badges34 silver badges55 bronze badges

It means that stderr (2 - containing error messages from the executed command or script) is redirected (>&) to stdout (1 - the output of the command) and that the latter is being redirected to /dev/null (the null device).

This way you can suppress all messages that might be issued by the executed command. In cron this is often done to avoid being spammed by lots of irrelevant messages from service scripts. Nevertheless be careful with this as some messages might be important.

More information on output redirects can be found in The Linux Documentation Project here and here. The null device is described here.

answered Aug 16, 2021 at 5:37

digijaydigijay

1,0743 gold badges9 silver badges22 bronze badges

Not the answer you're looking for? Browse other questions tagged centos cron or ask your own question.

What does >/ dev null 2 >& 1 mean?

What is meant by Dev Null?

What is the meaning of 2 >& 1 in Linux?

What does 2 mean in Linux?