At times you need to specify different courses of action to be taken in a shell script, depending on the success or failure of a command. The if construction allows you to specify such conditions.
The most compact syntax of the if command is:
if TEST-COMMANDS; then CONSEQUENT-COMMANDS; fi
The TEST-COMMAND list is executed, and if its return status is zero, the CONSEQUENT-COMMANDS list is executed. The return status is the exit status of the last command executed, or zero if no condition tested true.
The TEST-COMMAND often involves numerical or string comparison tests, but it can also be any command that returns a status of zero when it succeeds and some other status when it fails. Unary expressions are often used to examine the status of a file. If the FILE argument to one of the primaries is of the form /dev/fd/N, then file descriptor "N" is checked. stdin, stdout and stderr and their respective file descriptors may also be used for tests.
220.127.116.11. Expressions used with if
The table below contains an overview of the so-called "primaries" that make up the TEST-COMMAND command or list of commands. These primaries are put between square brackets to indicate the test of a conditional expression.
Table 7-1. Primary expressions
[ -aFILE ]
True if FILE exists.
[ -bFILE ]
True if FILE exists and is a block-special file.
[ -cFILE ]
True if FILE exists and is a character-special file.
[ -dFILE ]
True if FILE exists and is a directory.
[ -eFILE ]
True if FILE exists.
[ -fFILE ]
True if FILE exists and is a regular file.
[ -gFILE ]
True if FILE exists and its SGID bit is set.
[ -hFILE ]
True if FILE exists and is a symbolic link.
[ -kFILE ]
True if FILE exists and its sticky bit is set.
[ -pFILE ]
True if FILE exists and is a named pipe (FIFO).
[ -rFILE ]
True if FILE exists and is readable.
[ -sFILE ]
True if FILE exists and has a size greater than zero.
[ -tFD ]
True if file descriptor FD is open and refers to a terminal.
[ -uFILE ]
True if FILE exists and its SUID (set user ID) bit is set.
[ -wFILE ]
True if FILE True if FILE exists and is writable.
[ -xFILE ]
True if FILE exists and is executable.
[ -OFILE ]
True if FILE exists and is owned by the effective user ID.
[ -GFILE ]
True if FILE exists and is owned by the effective group ID.
[ -LFILE ]
True if FILE exists and is a symbolic link.
[ -NFILE ]
True if FILE exists and has been modified since it was last read.
[ -SFILE ]
True if FILE exists and is a socket.
[ FILE1-ntFILE2 ]
True if FILE1 has been changed more recently than FILE2, or if FILE1 exists and FILE2 does not.
[ FILE1-otFILE2 ]
True if FILE1 is older than FILE2, or is FILE2 exists and FILE1 does not.
[ FILE1-efFILE2 ]
True if FILE1 and FILE2 refer to the same device and inode numbers.
[ -o OPTIONNAME ]
True if shell option "OPTIONNAME" is enabled.
[ -z STRING ]
True of the length of "STRING" is zero.
[ -n STRING ] or [ STRING ]
True of the length of "STRING" is non-zero.
[ STRING1 == STRING2 ]
True if the strings are equal. "=" may be used instead of "==" for strict POSIX compliance.
[ STRING1 != STRING2 ]
True if the strings are not equal.
[ STRING1 < STRING2 ]
True if "STRING1" sorts before "STRING2" lexicographically in the current locale.
[ STRING1 > STRING2 ]
True if "STRING1" sorts after "STRING2" lexicographically in the current locale.
[ ARG1 OP ARG2 ]
"OP" is one of -eq, -ne, -lt, -le, -gt or -ge. These arithmetic binary operators return true if "ARG1" is equal to, not equal to, less than, less than or equal to, greater than, or greater than or equal to "ARG2", respectively. "ARG1" and "ARG2" are integers.
Expressions may be combined using the following operators, listed in decreasing order of precedence:
Table 7-2. Combining expressions
[ ! EXPR ]
True if EXPR is false.
[ ( EXPR ) ]
Returns the value of EXPR. This may be used to override the normal precedence of operators.
[ EXPR1 -a EXPR2 ]
True if both EXPR1 and EXPR2 are true.
[ EXPR1 -o EXPR2 ]
True if either EXPR1 or EXPR2 is true.
The [ (or test) built-in evaluates conditional expressions using a set of rules based on the number of arguments. More information about this subject can be found in the Bash documentation. Just like the if is closed with fi, the opening angular bracket should be closed after the conditions have been listed.
18.104.22.168. Commands following the then statement
The CONSEQUENT-COMMANDS list that follows the then statement can be any valid UNIX command, any executable program, any executable shell script or any shell statement, with the exception of the closing fi. It is important to remember that the then and fi are considered to be separated statements in the shell. Therefore, when issued on the command line, they are separated by a semi-colon.
In a script, the different parts of the if statement are usually well-separated. Below, a couple of simple examples.
22.214.171.124. Checking files
The first example checks for the existence of a file:
anny ~>cat msgcheck.sh
echo "This scripts checks the existence of the messages file."
if [ -f /var/log/messages ]
echo "/var/log/messages exists."
This scripts checks the existence of the messages file.
126.96.36.199. Checking shell options
To add in your Bash configuration files:
# These lines will print a message if the noclobber option is set:
if [ -o noclobber ]
echo "Your files are protected against accidental overwriting using redirection."
The above example will work when entered on the command line:
anny ~>if [ -o noclobber ] ; then echo ; echo "your files are protected
against overwriting." ; echo ; fi
your files are protected against overwriting.
However, if you use testing of conditions that depend on the environment, you might get different results when you enter the same command in a script, because the script will open a new shell, in which expected variables and options might not be set automatically.
7.1.2. Simple applications of if
188.8.131.52. Testing exit status
The ? variable holds the exit status of the previously executed command (the most recently completed foreground process).
The following example shows a simple test:
anny ~>if [ $? -eq 0 ]More input>then echo 'That was a good job!'More input>fi
That was a good job!
The following example demonstrates that TEST-COMMANDS might be any UNIX command that returns an exit status, and that if again returns an exit status of zero:
anny ~>if ! grep $USER/etc/passwdMore input>then echo "your user account is not managed locally"; fi
your user account is not managed locally
anny >echo $?
The same result can be obtained as follows:
anny >grep $USER/etc/passwdanny >if [ $? -ne 0 ] ; then echo "not a local account" ; fi
not a local account
184.108.40.206. Numeric comparisons
The examples below use numerical comparisons:
anny >num=`wc -l work.txt`anny >echo $num
anny >if [ "$num" -gt "150" ]More input>then echo ; echo "you've worked hard enough for today."More input>echo ; fi
you've worked hard enough for today.
This script is executed by cron every Sunday. If the week number is even, it reminds you to put out the garbage cans:
# Calculate the week number using the date command:
WEEKOFFSET=$[ $(date +"%V") % 2 ]
# Test if we have a remainder. If not, this is an even week so send a message.
# Else, do nothing.
if [ $WEEKOFFSET -eq "0" ]; then
echo "Sunday evening, put out the garbage cans." | mail -s "Garbage cans out" [email protected]_domain.org
220.127.116.11. String comparisons
An example of comparing strings for testing the user ID:
if [ "$(whoami)" != 'root' ]; then
echo "You have no permission to run $0 as non-root user."
With Bash, you can shorten this type of construct. The compact equivalent of the above test is as follows:
[ "$(whoami)" != 'root' ] && ( echo you are using a non-privileged account; exit 1 )
Similar to the "&&" expression which indicates what to do if the test proves true, "||" specifies what to do if the test is false.
Regular expressions may also be used in comparisons:
anny >gender="female"anny >if [[ "$gender" == f* ]]More input>then echo "Pleasure to meet you, Madame."; fi
Pleasure to meet you, Madame.
Most programmers will prefer to use the test built-in command, which is equivalent to using square brackets for comparison, like this:
test "$(whoami)" != 'root' && (echo you are using a non-privileged account; exit 1)
See the info pages for Bash for more information on pattern matching with the "(( EXPRESSION ))" and "[[ EXPRESSION ]]" constructs.