103.4. Use streams, pipes and redirects
Last updated
Last updated
Weight: 4
Description: Candidates should be able to redirect streams and connect them in order to efficiently process textual data. Tasks include redirecting standard input, standard output and standard error, piping the output of one command to the input of another command, using the output of one command as arguments to another command and sending output to both stdout and a file.
Key Knowledge Areas:
Redirecting standard input, standard output and standard error
Pipe the output of one command to the input of another command
Use the output of one command as arguments to another command
Send output to both stdout and a file
Terms and Utilities:
tee
xargs
We have talked about basics of piping and redirecting in previous sections and in this tutorial we take a closer look at Linux techniques for redirecting standard IO streams.
In computing, a stream is something that can transfer data. Data streams, like water streams, have two ends. They have a source and an outflow.
A Linux shell, such as Bash, receives input and sends output as sequences or streams of characters. Stream of characters comes from or goes to a file, a keyboard, a window on a display, or some other IO device.
stdin, stdout, and stederr are three standard streams that are established when a Linux command is executed.
Linux shells use these three standard I/O streams , each of which is associated with file descriptor::
stdout is the standard output stream, which displays output from commands(file descriptor 1)
stderr is the standard error stream, which displays error output from commands(file descriptor 2)
stdin is the standard input stream, which provides input to commands(file descriptor 0)
So we can see that there are two output streams, stdout and stderr, and one input stream, stdin
What are file descriptors?
Streams Are Handled Like Files. We can read text from a file, and we can write text into a file. Both of these actions involve a stream of data. So the concept of handling a stream of data as a file isn’t that much of a stretch.
Each file associated with a process is allocated a unique number to identify it.
This is known as the file descriptor. Whenever an action is required to be performed on a file, the file descriptor is used to identify the file. These values are always used for stdin, stdout, and stderr:
0: stdin
1: stdout
2: stderr
To make life more convenient the system creates some shortcuts for us:
Although the model for standard input and output is a serial stream of characters to and from a terminal, we might want to prepare input data in a file, or save output or error information in a file. That’s where .comes in.
There are two ways to redirect output to a file:
n> redirects output from file descriptor n to a file. You must have write authority to the file. If the file does not exist, it is created. If it does exist, the existing contents are usually lost without any warning.
n>> also redirects output from file descriptor n to a file. Again, we must have write authority to the file. If the file does not exist, it is created. If it does exist, the output is appended to the existing file.
The n in n> or n>> refers to the file descriptor. If it omitted, then standard output (file descriptor 1) is assumed.
The > and >> redirection symbols works with stdout by default. We can use one of the numeric file descriptors to indicate which standard output stream you wish to redirect.
> - standard output
2> - standard error
">" redirects stdout
"2>" redirects stderr
Append
Commands with a double bracket do not overwrite the destination’s existing contents, they append.
>> - standard output
2>> - standard error
To clobber or to noclobber?
We said that output redirection using n> usually overwrites existing files. You can control this with the noclobber option of the set builtin. use set -C for enabling noclobber:
If it has been set, we can override it using n>|
use set +C for turning globbing off.
redirect both standard output and standard error
Sometimes, we might want to redirect both standard output and standard error into a file. This is often done for automated processes or background jobs so that we can review the output later.
Use &> or &>> to redirect both standard output and standard error to the same place.
We can do it in another way, redirect file descriptor n and then redirect file descriptor m to the same place using the construct m>&n or m>>&n.
&1 and &2 and &0 reffer to current place of stdout , stderror and stdin.
The order in which outputs are redirected is important. For example,
command 2>&1 >output.txt
is not the same as
command >output.txt 2>&1
In the first case, stderr is redirected to the current location of stdout and then stdout is redirected to output.txt, but this second redirection affects only stdout, not stderr. In the second case, stderr is redirected to the current location of stdout and that is output.txt.
redirecting to /dev/null
At other times, we might want to ignore either standard output or standard error entirely. To do this, redirect the appropriate stream to the empty file, /dev/null.
/dev/null is a special file called the null device. it is also called the bit-bucket or the black-hole because it immediately discards anything written to it and only returns an end-of-file EOF when read.
"<" redirects stdin
or simply wc 0< list do the same thing.
A here document (or heredoc) is a way of getting text input into a script or command without having to feed it in from a separate file.
<< redirects standard input and the command will take input until "HeredocDelimiter" string .
Note: There should not be any space between the << symbol and the limit string. If there are any characters between the limit string and the << symbol then the here document is unlikely to work.
Reminder: "-" A hyphen (used alone) generally signifies that input will be taken from
stdinas opposed to a named file. try: cat - << EOF > interesting.txt
<<< Redirect a single line of text to the stdin of cmd. This is called a here-string.
We use the | (pipe) operator between two commands to direct the stdout of the first to the stdin of the second. command | command
Some commands like grep can accept input as parameters, but some commands accepts arguments
Parameter vs Argument:
Parameter is variable in the declaration of function.
Argument is the actual value of this variable that gets passed to function.
In the privious of pipelines, we learned how to take the output of one command and use it as input to another command. Instead , what if we want to use the output of a command or the contents of a file as arguments to a command rather than as input. Pipelines don’t work for that.
Three common methods are:
The xargs command
The find command with the -exec option (previous section)
Command substitution ( will be discussed later)
xargs is a Unix command which can be used to build and execute commands from standard input.
If no command is specified, xargs executes echo by default.
There are several ways in which xargs is useful in daily usage of the command line.
We can replace occurrences of arguments via -I switch:
it is also possible to run multiple commands with xargs
cat a.txt | xargs -I % sh -c {command1; command2; ... }
With -L option, the input will break by line and not by blanks. Other options:
xarg command example | Description |
xargs --version | Prints the version number of xargs command |
xargs -a test.txt | It will show contents of file |
xargs -p -a test.txt | -p option prompts for confirmation before running each command line. |
xargs -r -a test.txt | -r option ensures if standard input is empty, then command is not executed |
Sometimes we might want to see output on the screen while saving a copy for later. While we could do this by redirecting the command output to a file in one window and then using tail -f to follow the output in another screen, using the tee command is easier.
tee reads the standard input and writes it to both the standard output and one or more files.
tee always work after the '|' and it does both the tasks simultaneously.example:
with -a option It basically do not overwrite the file but append to the given file.
.
.
.
https://developer.ibm.com/tutorials/l-lpic1-103-4/
https://www.gnu.org/software/libc/manual/html_node/Streams-and-File-Descriptors.html
https://geek-university.com/linux/streams/
https://ryanstutorials.net/bash-scripting-tutorial/bash-input.php
https://www.howtogeek.com/435903/what-are-stdin-stdout-and-stderr-on-linux/
https://www.digitalocean.com/community/tutorials/an-introduction-to-linux-i-o-redirection
https://www.serverwatch.com/columns/article.php/3860446/Shell-Scripts-and-Here-Documents.htm
https://linuxhint.com/bash-heredoc-tutorial/
https://stackoverflow.com/questions/40230008/whats-the-usages-of-hyphen-in-linux-shell
https://www.geeksforgeeks.org/xargs-command-unix/
https://www.tecmint.com/xargs-command-examples/
.
