{"id":51,"date":"2018-10-10T16:34:00","date_gmt":"2018-10-10T08:34:00","guid":{"rendered":"https:\/\/yeslq.com\/20181051.html"},"modified":"2018-11-11T16:11:07","modified_gmt":"2018-11-11T08:11:07","slug":"the-linux-command-line-i-o-redirection","status":"publish","type":"post","link":"https:\/\/yeslq.com\/?p=51","title":{"rendered":"The Linux Command Line—I\/O Redirection"},"content":{"rendered":"

The Linux Command Line <\/a><\/i>by William Shotts<\/span><\/h1>\n

<\/span><\/div>\n
<\/p>\n
In this lesson, we will explore a powerful feature used by many command line programs called input\/output redirection<\/i>. As we have seen, many commands such as ls<\/tt> print their output on the display. This does not have to be the case, however. By using some special notations we can redirect<\/i> the output of many commands to files, devices, and even to the input of other commands.<\/div>\n

Standard Output<\/span><\/h2>\n
Most command line programs that display their results do so by sending their results to a facility called standard output<\/i>. By default, standard output directs its contents to the display. To redirect standard output to a file, the “>” character is used like this:<\/div>\n
[me@linuxbox me]$<\/tt> ls > file_list.txt<\/tt><\/div>\n
In this example, the ls<\/tt> command is executed and the results are written in a file named file_list.txt. Since the output of ls<\/tt> was redirected to the file, no results appear on the display.<\/div>\n
Each time the command above is repeated, file_list.txt is overwritten from the beginning with the output of the command ls<\/tt>. If you want the new results to be appended<\/i> to the file instead, use “>>” like this:<\/div>\n
[me@linuxbox me]$<\/tt> ls >> file_list.txt<\/tt><\/div>\n
When the results are appended, the new results are added to the end of the file, thus making the file longer each time the command is repeated. If the file does not exist when you attempt to append the redirected output, the file will be created.<\/div>\n

Standard Input<\/span><\/h2>\n
Many commands can accept input from a facility called standard input<\/i>. By default, standard input gets its contents from the keyboard, but like standard output, it can be redirected. To redirect standard input from a file instead of the keyboard, the “<” character is used like this:<\/div>\n
[me@linuxbox me]$<\/tt> sort < file_list.txt<\/tt><\/div>\n
In the example above, we used the sort<\/a><\/tt> command to process the contents of file_list.txt. The results are output on the display since the standard output was not redirected. We could redirect standard output to another file like this:<\/div>\n
[me@linuxbox me]$<\/tt> sort < file_list.txt > sorted_file_list.txt<\/tt><\/div>\n
As you can see, a command can have both its input and output redirected. Be aware that the order of the redirection does not matter. The only requirement is that the redirection operators (the “<” and “>”) must appear after the other options and arguments in the command.<\/div>\n

Pipelines<\/span><\/h2>\n
The most useful and powerful thing you can do with I\/O redirection is to connect multiple commands together with what are called pipelines<\/i>. With pipelines, the standard output of one command is fed into the standard input of another. Here is my absolute favorite:<\/div>\n
[me@linuxbox me]$<\/tt> ls -l | less<\/tt><\/div>\n
In this example, the output of the ls<\/tt> command is fed into less<\/tt>. By using this \"| less\"<\/tt> trick, you can make any command have scrolling output. I use this technique all the time.<\/div>\n
By connecting commands together, you can acomplish amazing feats. Here are some examples you’ll want to try:<\/div>\n\n\n\n\n\n\n
Examples of commands used together with pipelines<\/caption>\n
Command<\/strong><\/th>\nWhat it does<\/strong><\/th>\n<\/tr>\n
ls -lt | head<\/a><\/tt><\/td>\nDisplays the 10 newest files in the current directory.<\/td>\n<\/tr>\n
du<\/a> | sort -nr<\/tt><\/td>\nDisplays a list of directories and how much space they consume, sorted from the largest to the smallest.<\/td>\n<\/tr>\n
find<\/a> . -type f -print | wc<\/a> -l<\/tt><\/td>\nDisplays the total number of files in the current working directory and all of its subdirectories.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Filters<\/span><\/a><\/h2>\n
One kind of program frequently used in pipelines is called filters<\/i>. Filters take standard input and perform an operation upon it and send the results to standard output. In this way, they can be combined to process information in powerful ways. Here are some of the common programs that can act as filters:<\/div>\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Common filter commands<\/caption>\n
Program<\/strong><\/th>\nWhat it does<\/strong><\/th>\n<\/tr>\n
sort<\/a><\/tt><\/td>\nSorts standard input then outputs the sorted result on standard output.<\/td>\n<\/tr>\n
uniq<\/a><\/tt><\/td>\nGiven a sorted stream of data from standard input, it removes duplicate lines of data (i.e., it makes sure that every line is unique).<\/td>\n<\/tr>\n
grep<\/a><\/tt><\/td>\nExamines each line of data it receives from standard input and outputs every line that contains a specified pattern of characters.<\/td>\n<\/tr>\n
fmt<\/a><\/tt><\/td>\nReads text from standard input, then outputs formatted text on standard output.<\/td>\n<\/tr>\n
pr<\/a><\/tt><\/td>\nTakes text input from standard input and splits the data into pages with page breaks, headers and footers in preparation for printing.<\/td>\n<\/tr>\n
head<\/a><\/tt><\/td>\nOutputs the first few lines of its input. Useful for getting the header of a file.<\/td>\n<\/tr>\n
tail<\/a><\/tt><\/td>\nOutputs the last few lines of its input. Useful for things like getting the most recent entries from a log file.<\/td>\n<\/tr>\n
tr<\/a><\/tt><\/td>\nTranslates characters. Can be used to perform tasks such as upper\/lowercase conversions or changing line termination characters from one type to another (for example, converting DOS text files into Unix style text files).<\/td>\n<\/tr>\n
sed<\/a><\/tt><\/td>\nStream editor. Can perform more sophisticated text translations than tr<\/tt>.<\/td>\n<\/tr>\n
awk<\/a><\/tt><\/td>\nAn entire programming language designed for constructing filters. Extremely powerful.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n


<\/p>\n

\n

Performing tasks with pipelines<\/span><\/h2>\n
    \n
  1. Printing from the command line.<\/strong> Linux provides a program called lpr<\/a><\/tt> that accepts standard input and sends it to the printer. It is often used with pipes and filters. Here are a couple of examples:\n

    cat poorly_formatted_report.txt | fmt | pr | lpr

    cat unsorted_list_with_dupes.txt | sort | uniq | pr | lpr
    <\/tt>
    <\/pre>\n
    In the first example, we use cat<\/tt> to read the file and output it to standard output, which is piped into the standard input of fmt. fmt<\/tt> formats the text into neat paragraphs and outputs it to standard output, which is piped into the standard input of pr. pr<\/tt> splits the text neatly into pages and outputs it to standard output, which is piped into the standard input of lpr. lpr<\/tt> takes its standard input and sends it to the printer.
    The second example starts with an unsorted list of data with duplicate entries. First, cat<\/tt> sends the list into sort<\/tt> which sorts it and feeds it into uniq<\/tt>which removes any duplicates. Next pr<\/tt> and lpr<\/tt> are used to paginate and print the list.<\/li>\n
  2. Viewing the contents of tar files<\/strong> Often you will see software distributed as a gzipped tar file<\/i>. This is a traditional Unix style tape archive file (created with tar<\/a><\/tt>) that has been compressed with gzip<\/a><\/tt>. You can recognize these files by their traditional file extensions, “.tar.gz” or “.tgz”. You can use the following command to view the directory of such a file on a Linux system:\n
    tar tzvf name_of_file.tar.gz | less
    <\/tt>
    <\/pre>\n
    <\/li>\n<\/ol>\n<\/div>\n
    \n
    <\/div>\n<\/div>\n
    <\/span><\/div>\n","protected":false},"excerpt":{"rendered":"
    The Linux Command Line by William Shotts In this l … \u9605\u8bfb\u66f4\u591a<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,4,6],"tags":[],"class_list":["post-51","post","type-post","status-publish","format-standard","hentry","category-linux","category-shell","category-the-linux-command-line"],"_links":{"self":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/51","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=51"}],"version-history":[{"count":1,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/51\/revisions"}],"predecessor-version":[{"id":113,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/51\/revisions\/113"}],"wp:attachment":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=51"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=51"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=51"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}