Checking the success of a command in a bash `if [ .. ]` statement

by

You are making the common mistake of assuming that [ is part of the if statement’s syntax. It is not; the syntax of if is simply

if command; then
    : # ... things which should happen if command's result code was 0
else
    : # ... things which should happen otherwise
fi

One of the common commands we use is [ which is an alias for the command test. It is a simple command for comparing strings, numbers, and files. It accepts a fairly narrow combination of arguments, and tends to generate confusing and misleading error messages if you don’t pass it the expected arguments. (Or rather, the error messages are adequate and helpful once you get used to it, but they are easily misunderstood if you’re not used.)

Here, you want to check the result of the command egrep:

if [ ! -f /opt/apps/SiteScope_backup/sitescope_configuration.zip ] ||
   egrep -i -q "error|warning|fatal|missing|critical" "$File"
then
    echo "testing"
fi

In the general case, command can be a pipeline or a list of commands; then, the exit code from the final command is the status which if will examine, similarly to how the last command in a script decides the exit status from the script.

These compound commands can be arbitrarily complex, like

if read thing
    case $thing in
      '' | 'quit') false;;
      *) true;;
    esac
then ...

but in practice, you rarely see more than a single command in the if statement (though it’s not unheard of; your compound statement with || is a good example!)

Just to spell this out,

if [ egrep foo bar ]

is running [ aka test on the arguments egrep foo bar. But [ without options only accepts a single argument, and then checks whether or not that argument is the empty string. (egrep is clearly not an empty string. Quoting here is optional, but would perhaps make it easier to see:

if [ "egrep" ]; then
    echo "yes, 'egrep' is not equal to ''"
fi

This is obviously silly in isolation, but should hopefully work as an illustrative example.)

The historical reasons for test as a general kitchen sink of stuff the authors didn’t want to make part of the syntax of if is one of the less attractive designs of the original Bourne shell. Bash and zsh offer alternatives which are less unwieldy (like the [[ double brackets in bash), and of course, POSIX test is a lot more well-tempered than the original creation from Bell Labs.

More Related Contents:

  1. Why should there be spaces around ‘[‘ and ‘]’ in Bash?
  2. How do I compare two string variables in an ‘if’ statement in Bash? [duplicate]
  3. Are double square brackets [[ ]] preferable over single square brackets [ ] in Bash?
  4. When are square brackets required in a Bash if statement?
  5. Is there a list of ‘if’ switches anywhere?
  6. Test for non-zero length string in Bash: [ -n “$var” ] or [ “$var” ]
  7. Meaning of “[: too many arguments” error from if [] (square brackets)
  8. Difference between single and double square brackets in Bash
  9. How to check the exit status using an ‘if’ statement
  10. Compound ‘if’ statements with multiple expressions in Bash
  11. Floating point comparison with variable in bash [duplicate]
  12. Using the && operator in an if statement
  13. How to do a logical OR operation for integer comparison in shell scripting?
  14. Bash if statement with multiple conditions throws an error
  15. Reading key/value parameters from a file into a shell script
  16. if, elif, else statement issues in Bash
  17. Validate date format in a shell script
  18. Groups of compound conditions in Bash test [duplicate]
  19. How to determine the current interactive shell that I’m in (command-line)
  20. Removing colors from output
  21. How to loop through a directory recursively to delete files with certain extensions
  22. Associative arrays in Shell scripts
  23. How can I remove the first line of a text file using bash/sed script?
  24. How to get the part of a file after the first line that matches a regular expression
  25. How can I reference a file for variables using Bash?
  26. Why is this bash prompt acting strangely/disappearing, and how do I fix it (OS X)?
  27. Bash: Copy named files recursively, preserving folder structure
  28. What does “export” do in shell programming? [duplicate]
  29. What is the most elegant way to remove a path from the $PATH variable in Bash?
  30. How to match a single quote in sed

Leave a Comment