The past few chapters have gone into detail about various shell programming techniques, mostly focused on the flow of data and control through shell programs. In this chapter, we'll switch the focus to two related topics. The first is the shell's mechanisms for doing file-oriented input and output. We'll present information that expands on what you already know about the shell's basic I/O redirectors.
Second, we'll "zoom in" and talk about I/O at the line and word level. This is a fundamentally different topic, since it involves moving information between the domains of files/terminals and shell variables. print and command substitution are two ways of doing this that we've seen so far.
Our discussion of line and word I/O will lead into a more detailed explanation of how the shell processes command lines. This information is necessary so that you can understand exactly how the shell deals with quotation , and so that you can appreciate the power of an advanced command called eval , which we will cover at the end of the chapter.
In Chapter 1, Korn Shell Basics you learned about the shell's basic I/O redirectors, > , < , and | . Although these are enough to get you through 95% of your UNIX life, you should know that the Korn shell supports a total of 16 I/O redirectors. Table 7.1 lists them, including the three we've already seen. Although some of the rest are useful, others are mainly for systems programmers. We will wait until the next chapter to discuss the last three, which, along with >| , are not present in most Bourne shell versions.
Notice that some of the redirectors in Table 7.1 contain a digit n , and that their descriptions contain the term file descriptor ; we'll cover that in a little while.
The first two new redirectors, >> and >| , are simple variations on the standard output redirector > . The >> appends to the output file (instead of overwriting it) if it already exists; otherwise it acts exactly like > . A common use of >> is for adding a line to an initialization file (such as .profile or .mailrc ) when you don't want to bother with a text editor. For example:
cat >> .mailrc alias fred firstname.lastname@example.org ^D
As we saw in Chapter 1 , cat without an argument uses standard input as its input. This allows you to type the input and end it with [CTRL-D] on its own line. The alias line will be appended to the file .mailrc if it already exists; if it doesn't, the file is created with that one line.
Recall from Chapter 3, Customizing Your Environment that you can prevent the shell from overwriting a file with > file by typing set -o noclobber . >| overrides noclobber - it's the "Do it anyway, dammit!" redirector.
The redirector <> is mainly meant for use with device files (in the /dev directory), i.e., files that correspond to hardware devices such as terminals and communication lines. Low-level systems programmers can use it to test device drivers; otherwise, it's not very useful. But if you use a windowing system like X, you can try the following to see how it works:
The << label redirector essentially forces the input to a command to be the shell's standard input, which is read until there is a line that contains only label . The input in between is called a here-document . Here-documents aren't very interesting when used from the command prompt. In fact, it's the same as the normal use of standard input except for the label. We could have used a here-document in the previous example of >> , like this (EOF, for "end of file," is an often-used label):
cat >> .mailrc << EOF alias fred email@example.com EOF
Here-documents are meant to be used from within shell scripts; they let you specify "batch" input to programs. A common use of here-documents is with simple text editors like ed(1) . Here is a programming task that uses a here-document in this way:
We can use
to delete the header lines.
To do this, we need to know something about the syntax of mail messages;
specifically, that there is always a blank line between the header lines
and the message text.
ed $1 << EOF 1,/^*$/d w q EOF
The shell does parameter (variable) substitution and command substitution on text in a here-document, meaning that you can use shell variables and commands to customize the text. Here is a simple task for system administrators that shows how this works:
You can get a list of all users on the system in various ways;
perhaps the easiest is to use
extract the first field of
the file that contains all user account information. Fields in
this file are separated by colons (
Given such a list of users, the following code does the trick:
pgmname=$1 for user in $(cut -f1 -d: /etc/passwd); do mail $user << EOF Dear $user, A new version of $pgmname has been installed in $(whence pgmname). Regards, Your friendly neighborhood sysadmin. EOF done
The shell will substitute the appropriate values for the name of the program and its directory.
has two variations. First, you can
prevent the shell from doing parameter and command substitution by surrounding
in single or double quotes. In the above example, if you
used the line
The second variation is <<- , which deletes leading TABs (but not blanks) from the here-document and the label line. This allows you to indent the here-document's text, making the shell script more readable:
pgmname=$1 for user in $(cut -f1 -d: /etc/passwd); do mail $user <<- EOF Dear user, A new version of $pgmname has been installed in $(whence pgmname). Regards, Your friendly neighborhood sysadmin. EOF done
The next few redirectors in Table 7.1 depend on the notion of a file descriptor . Like the device files used with <> , this is a low-level UNIX I/O concept that is of interest only to systems programmers - and then only occasionally. File descriptors are historical relics that really should be banished from the realm of shell use.  You can get by with a few basic facts about them; for the whole bloody story, look at the entries for read (), write (), fcntl (), and others in Section 2 of the UNIX manual.
File descriptors are integers starting at 0 that index an array of file information within a process. When a process starts, it usually has three file descriptors open. These correspond to the three standards : standard input (file descriptor 0), standard output (1), and standard error (2). If a process opens UNIX files for input or output, they are assigned to the next available file descriptors, starting with 3.
By far the most common use of file descriptors with the Korn shell is in saving standard error in a file. For example, if you want to save the error messages from a long job in a file so that they don't scroll off the screen, append 2> file to your command. If you also want to save standard output, append > file1 2> file2 .
This leads to another programming task.
We'll call this script start . The code is very terse:
"$@" > logfile 2>&1 &
This line executes whatever command and parameters follow start . (The command cannot contain pipes or output redirectors.) It sends the command's standard output to logfile .
Then, the redirector 2>&1 says, "send standard error (file descriptor 2) to the same place as standard output (file descriptor 1)." 2>&1 is actually a combination of two redirectors in Table 7.1 : n > file and >& n . Since standard output is redirected to logfile , standard error will go there too. The final & puts the job in the background so that you get your shell prompt back.
As a small variation on this theme, we can send both standard output and standard error into a pipe instead of a file: command 2>&1 | ... does this. (Make sure you understand why.) Here is a script that sends both standard output and standard error to the logfile (as above) and to the terminal:
"$@" 2>&1 | tee logfile &
These scripts have one shortcoming: you must remain logged in until the job completes. Although you can always type jobs (see Chapter 1 ) to check on progress, you can't leave your office for the day unless you want to risk a breach of security or waste electricity. We'll see how to solve this problem in the next chapter.
The other file-descriptor-oriented redirectors (e.g., <& n ) are usually used for reading input from (or writing output to) more than one file at the same time. We'll see an example later in this chapter. Otherwise, they're mainly meant for systems programmers, as are <&- (force standard input to close) and >&- (force standard output to close).