{"id":34,"date":"2018-10-22T08:00:00","date_gmt":"2018-10-22T00:00:00","guid":{"rendered":""},"modified":"2018-11-11T16:10:58","modified_gmt":"2018-11-11T08:10:58","slug":"the-linux-command-line-errors-and-signals-and-traps-oh-my-part-1","status":"publish","type":"post","link":"https:\/\/yeslq.com\/?p=34","title":{"rendered":"The Linux Command Line—Errors And Signals And Traps (Oh My!) – Part 1"},"content":{"rendered":"

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

<\/span><\/div>\n
<\/p>\n
In this lesson, we’re going to look at handling errors during the execution of your scripts.<\/div>\n
The difference between a good program and a poor one is often measured in terms of the program’s robustness<\/i>. That is, the program’s ability to handle situations in which something goes wrong.<\/div>\n

Exit Status<\/h2>\n
As you recall from previous lessons, every well-written program returns an exit status when it finishes. If a program finishes successfully, the exit status will be zero. If the exit status is anything other than zero, then the program failed in some way.<\/div>\n
It is very important to check the exit status of programs you call in your scripts. It is also important that your scripts return a meaningful exit status when they finish. I once had a Unix system administrator who wrote a script for a production system containing the following 2 lines of code:<\/div>\n
\n
# Example of a really bad idea

cd $some_directory
rm *<\/tt><\/pre>\n<\/div>\n
Why is this such a bad way of doing it? It’s not, if nothing goes wrong. The two lines change the working directory to the name contained in $some_directory<\/tt>and delete the files in that directory. That’s the intended behavior. But what happens if the directory named in $some_directory<\/tt> doesn’t exist? In that case, the cd<\/tt> command will fail and the script executes the rm<\/tt> command on the current working directory. Not the intended behavior!<\/div>\n
By the way, my hapless system administrator’s script suffered this very failure and it destroyed a large portion of an important production system. Don’t let this happen to you!<\/div>\n
The problem with the script was that it did not check the exit status of the cd<\/tt> command before proceeding with the rm<\/tt> command.<\/div>\n
Checking The Exit Status<\/h2>\n
There are several ways you can get and respond to the exit status of a program. First, you can examine the contents of the $?<\/tt> environment variable. $?<\/tt> will contain the exit status of the last command executed. You can see this work with the following:<\/div>\n
\n
[me] $<\/tt> true; echo $?<\/tt>
0
[me] $<\/tt> false; echo $?<\/tt>
1<\/tt><\/pre>\n<\/div>\n
The true<\/tt> and false<\/tt> commands are programs that do nothing except return an exit status of zero and one, respectively. Using them, we can see how the $?<\/tt>environment variable contains the exit status of the previous program.<\/div>\n
So to check the exit status, we could write the script this way:<\/div>\n
\n
# Check the exit status

cd<\/tt> $some_directory
if<\/tt> [<\/tt> \"$?\" = \"0\" ];<\/tt> then<\/tt>
 rm *
else<\/tt>
 echo<\/tt> \"Cannot change directory!\" 1>&2
 exit<\/tt> 1
fi<\/tt>
<\/tt><\/pre>\n<\/div>\n
In this version, we examine the exit status of the cd<\/tt> command and if it’s not zero, we print an error message on standard error and terminate the script with an exit status of 1.<\/div>\n
While this is a working solution to the problem, there are more clever methods that will save us some typing. The next approach we can try is to use the if<\/tt>statement directly, since it evaluates the exit status of commands it is given.<\/div>\n
Using if<\/tt>, we could write it this way:<\/div>\n
\n
# A better way

if<\/tt> cd<\/tt> $some_directory; then<\/tt>
 rm *
else<\/tt>
 echo<\/tt> \"Could not change directory! Aborting.\" 1>&2
 exit<\/tt> 1
fi<\/tt>
<\/tt><\/pre>\n<\/div>\n
Here we check to see if the cd<\/tt> command is successful. Only then does rm<\/tt> get executed; otherwise an error message is output and the program exits with a code of 1, indicating that an error has occurred.<\/div>\n
An Error Exit Function<\/h2>\n
Since we will be checking for errors often in our programs, it makes sense to write a function that will display error messages. This will save more typing and promote laziness.<\/div>\n
\n
# An error exit function

error_exit()
{
 echo<\/tt> \"$1\" 1>&2
 exit<\/tt> 1
}

# Using error_exit

if<\/tt> cd<\/tt> $some_directory; then<\/tt>
 rm *
else<\/tt>
 error_exit \"Cannot change directory!  Aborting.\"
fi<\/tt>
<\/tt><\/pre>\n<\/div>\n
AND And OR Lists<\/h2>\n
Finally, we can further simplify our script by using the AND and OR control operators. To explain how they work, I will quote from the bash<\/a><\/tt> man page:<\/div>\n
“The control operators && and || denote AND lists and OR lists, respectively. An AND list has the form<\/div>\n
command1 && command2<\/tt><\/div>\n
command2<\/tt> is executed if, and only if<\/i>, command1<\/tt> returns an exit status of zero.<\/div>\n
An OR list has the form<\/div>\n
command1 || command2<\/tt><\/div>\n
command2<\/tt> is executed if, and only if, command1<\/tt> returns a non-zero exit status. The exit status of AND and OR lists is the exit status of the last command executed in the list.”<\/div>\n
Again, we can use the true<\/tt> and false<\/tt> commands to see this work:<\/div>\n
\n
[me] $<\/tt> true || echo \"echo executed\"<\/tt>
[me] $<\/tt> false || echo \"echo executed\"<\/tt>
echo executed<\/tt>
[me] $<\/tt> true && echo \"echo executed\"<\/tt>
echo executed<\/tt>
[me] $<\/tt> false && echo \"echo executed\"<\/tt>
[me] $<\/tt><\/tt><\/pre>\n<\/div>\n
Using this technique, we can write an even simpler version:<\/div>\n
\n
# Simplest of all

cd<\/tt> $some_directory || error_exit \"Cannot change directory! Aborting\"
rm *
<\/tt><\/pre>\n<\/div>\n
If an exit is not required in case of error, then you can even do this:<\/div>\n
\n
# Another way to do it if exiting is not desired

cd<\/tt> $some_directory && rm *
<\/tt><\/pre>\n<\/div>\n
I want to point out that even with the defense against errors we have introduced in our example for the use of cd<\/tt>, this code is still vulnerable to a common programming error, namely, what happens if the name of the variable containing the name of the directory is misspelled? In that case, the shell will interpret the variable as empty and the cd<\/tt> succeed, but it will change directories to the user’s home directory, so beware!<\/div>\n
Improving The Error Exit Function<\/h2>\n
There are a number of improvements that we can make to the error_exit<\/tt> function. I like to include the name of the program in the error message to make clear where the error is coming from. This becomes more important as your programs get more complex and you start having scripts launching other scripts, etc. Also, note the inclusion of the LINENO<\/tt> environment variable which will help you identify the exact line within your script where the error occurred.<\/div>\n
\n
#!\/bin\/bash

# A slicker error handling routine

# I put a variable in my scripts named PROGNAME which
# holds the name of the program being run.  You can get this
# value from the first item on the command line ($0).

PROGNAME=$(basename $0)

error_exit()
{

# ----------------------------------------------------------------
# Function for exit due to fatal program error
#  Accepts 1 argument:
#   string containing descriptive error message
# ----------------------------------------------------------------


 echo<\/tt> \"${PROGNAME}: ${1:-\"Unknown Error\"}\" 1>&2
 exit<\/tt> 1
}

# Example call of the error_exit function.  Note the inclusion
# of the LINENO environment variable.  It contains the current
# line number.

echo<\/tt> \"Example of error with line number and message\"
error_exit \"$LINENO: An error has occurred.\"
<\/tt><\/pre>\n<\/div>\n
The use of the curly braces within the error_exit<\/tt> function is an example of parameter expansion<\/i>. You can surround a variable name with curly braces (as with ${PROGNAME}<\/tt>) if you need to be sure it is separated from surrounding text. Some people just put them around every variable out of habit. That usage is simply a style thing. The second use, ${1:-\"Unknown Error\"}<\/tt> means that if parameter 1 ($1<\/tt>) is undefined, substitute the string “Unknown Error” in its place. Using parameter expansion, it is possible to perform a number of useful string manipulations. You can read more about parameter expansion in the bash<\/a><\/tt> man page under the topic “EXPANSIONS”.<\/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":[5,3,4,6],"tags":[],"class_list":["post-34","post","type-post","status-publish","format-standard","hentry","category-error","category-linux","category-shell","category-the-linux-command-line"],"_links":{"self":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/34","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=34"}],"version-history":[{"count":1,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/34\/revisions"}],"predecessor-version":[{"id":95,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/34\/revisions\/95"}],"wp:attachment":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=34"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=34"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=34"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}