In bash, standard (1) and error (2) output can be re-routed and discarded with:
>/dev/null 2>&1
But the following example does s
It is a way to close stdin
, as if EOF
(^D
) were sent to it. It can be used as in this example with the mail command to signify it that the command should no more expect input from stdin
.
It is also often used to daemonize processes (Stop 6 of the recommended approach for creating well-behaved daemons)
</dev/null
is used to avoid the script wait for input.
Quoting from the usage of < /dev/null & in the command line:
< /dev/null
is used to instantly send EOF to the program, so that it doesn't wait for input (/dev/null
, the null device, is a special file that discards all data written to it, but reports that the write operation succeeded, and provides no data to any process that reads from it, yielding EOF immediately).&
is a special type of command separator used to background the preceding process.
So the command:
nohup myscript.sh >myscript.log 2>&1 </dev/null &
# | ^^^^^^^^^^^^^ ^^^^ ^^^^^^^^^^ ^
# | | | | run in background
# | | | |
# | | | don't expect input
# | | |
# | | redirect stderr to stdout
# | |
# | redirect stdout to myscript.log
# |
# keep running the command no matter the connection is lost or you logout
will move to background the command, outputing both stdout and stderr to myscript.log
without waiting for any input.
Redirecting /dev/null
to stdin will give an immediate EOF
to any read call from that process. This is typically useful to detach a process from a tty (such a process is called a daemon). For example, when starting a background process remotely over ssh, you must redirect stdin to prevent the process waiting for local input.
Another reason to redirect to /dev/null is to prevent an unused file descriptor being created for stdin. This can minimize the total open file handles when you have many long running processes.
</dev/null
provides empty input to the script...