Error stream operating in the example
Stderr is very similar to stdout: with only one difference – it will contain an error report if it will take a place
script body:
#!/usr/bin/env bash
ls > /tmp/log
cat /tmp/log
ls /not/existed_path > /tmp/log
cat /tmp/log
cat /tmp/log
rm /tmp/log
The script running at the console:
At this script, we make a listing of files in the current directory (“ls”) and redirect standard output to the file (“/tmp/log”). Then we display this file data at the console from the standard output stream of the cat utility that read the file. Next, we try to list files in the not existing folder and store results into the file as above, and display it two times. But there is no effect. Just one output about the error in the console. That is because this error comes from the standard errors stream of ls. We removed the file to clear some space “/tmp/log“.
Shell Scripting – Standard Input, Output and Error
Working on Linux applications we have several ways to get information from outside and to put it inside: command line args, environment variables, files. All of these sources are legal and good. But it has a finite size. Another way to establish communication is standard streams: input stream (stdin) used for getting data from outside of the app, output stream (stdout) to put data outside of the app, and error to put data outside of the app (stderr).
Each stream acts like a pipe: It has the same buffer to write and read the data. This buffer is available for reading from one application and available for writing from another one. On reading, the occupied buffer size will be reduced and it will be increased on writing. If the average rate of reading and writing is equal – then data passed over the stream can be any number of bytes long.
Table of Content
- Input/output streams operating in the example
- Error stream operating in the example
- Streams redirecting
- Discard the output
- Pipelined streams
- Here document
- Shell Scripting – Standard Input, Output and Error – FAQs
Contact Us