≡ Menu

Shell: How to determine the exit status of Linux and UNIX command

Q. Can you explain the exit status of shell and commands under Linux / UNIX operating system?

A. All UNIX and Linux command has a several parameters or variables that can be use to find out the exit status of command. Please note that these parameters or variables may only be referenced assignment to them is not allowed. You can use $? to find out the exit status of command. $? always expands to the status of the most recently executed foreground command or pipeline. For example, you run the command cal:
$ cal
Now to see exit status of cal command type following command:
$ echo $?


Zero means command executed successfully, if exit status returns non-zero value then your command failed to execute. For example run command called cyberciti
$ cyberciti

bash: cyberciti: command not found

Display exit status of the command:
$ echo $?


Value 127 (non-zero) indicates command cyberciti failed to execute. You can use exit status in shell scripting too. You can store result of exit status in variable. Consider following shell script:

echo -n "Enter user name : "
read USR
cut -d: -f1 /etc/passwd | grep "$USR" > /dev/null
if [ $OUT -eq 0 ];then
   echo "User account found!"
   echo "User account does not exists in /etc/passwd file!"

Save and execute the script as follows:
$ chmod +x script.sh
$ ./script.sh


Enter user name : jradmin
User account does not exists in /etc/passwd file

Try it one more time:
$ ./script.sh

Enter user name : vivek
User account found

As you can see, I have used grep command to find out user name stored in USR variable. If grep command finds user name in /etc/passwd command output it would return exit status of zero. This is stored in OUT variable. Next, if command makes decision based upon exit status stored in OUT variable.

Share this tutorial on:

Your support makes a big difference:
I have a small favor to ask. More people are reading the nixCraft. Many of you block advertising which is your right, and advertising revenues are not sufficient to cover my operating costs. So you can see why I need to ask for your help. The nixCraft, takes a lot of my time and hard work to produce. If you use nixCraft, who likes it, helps me with donations:
Become a Supporter →    Make a contribution via Paypal/Bitcoin →   

Don't Miss Any Linux and Unix Tips

Get nixCraft in your inbox. It's free:

{ 18 comments… add one }
  • Rob April 3, 2007, 6:54 pm

    Mate, I followed your script and it says “can’t execute binaries?

    Don’t know seem pretty good, but doesn’t quite get there for me.
    I am running Ubuntu Dapper Drake Linux.

    Keep it coming, it is good stuff.


  • Rob April 3, 2007, 6:59 pm

    G’day again,

    Nope, I was wrong the script works I didn’t copy it properly. I left out the #!/bin/bash.


    Love your work.


  • moheb April 5, 2008, 3:55 pm

    thank you

    it seems very useful for my search
    great job

  • powerpleb June 1, 2008, 10:27 am

    Thanks a lot. Useful info and explained well!

  • mike July 18, 2008, 4:54 am

    im a newbie in AIX platform. Just want to ask how to execute this command: #!/bin/bash

  • Poonam August 5, 2008, 12:16 pm

    Can you tell me what ist he difference between return status of 1 and 8. I tries to search but could not find it on web….

  • nixCraft August 5, 2008, 1:00 pm

    Exit status is depend upon program or command. Read man page to find out meaning of return status 1 and 8.

  • Poonam August 20, 2008, 8:22 am

    I tried to find out, but did not find anything. We are using bourne shell….If in my shell script I am exiting with return status of 1 or 8, what difference will it make…

  • chris neale July 17, 2010, 4:52 pm

    $ ./cyberciti; echo $?
    -bash: ./cyberciti: No such file or directory

    $ ssh localhost “./cyberciti; echo $?”
    bash: ./cyberciti: No such file or directory


    • tuh July 12, 2011, 5:45 pm

      Maybe Chris will see this, or maybe not. Anyway…

      The reason you get an exit code of “0” on that last one is that ssh was successful in connecting to localhost and executing your command. The command itself failed. But ssh worked. So, ssh returns zero in that instance. Exit codes don’t call back from internal commands. Look at this for instance:
      $ ls filenotfound.txt; echo $?
      ls: cannot access filenotfound.txt…
      $ ls filenotfound.txt &
      ls: cannot access filenotfound.txt…
      echo $?
      [2]+ Exit 2 ls filenotfound.txt

      Same thing happens when you fork off a process. You successfully submitted the job, so you get a zero exit code.

      • Erik February 15, 2016, 2:40 pm

        $ ssh localhost “./cyberciti; echo $?” Did you notice it was all in quotes?

  • M P November 9, 2010, 1:23 pm

    Very helpful. Thanks very much.

  • saravanakumar June 12, 2011, 2:44 pm

    Very useful…thanks a lot…its makes me to understand about “$?”.

  • wjuarezq October 27, 2011, 8:11 am

    The script has a bug: If your acount is “vivek” and you type “viv” that say you “User account found”, you can solve it with this:
    cut -d: -f1 /etc/passwd | grep “^””$USR””$” > /dev/null

  • Toby Ho February 6, 2012, 4:15 am

    Thanks! That helped.

  • Thayananth September 20, 2012, 11:23 am

    I need to know the return values which we get after executing the run command in UNIX.
    I know only 0 for successful. What are the other values present.
    Also, could anyone tell me about the description of those errors.


  • Rahul Jawale December 17, 2012, 11:55 am

    You are doing good work. Thank you!!

  • davb March 6, 2013, 4:05 pm

    Actually, rather than grep “^””$USR””$”, just use grep -w $USR ….easy!

Leave a Comment

You can use these HTML tags and attributes: <strong> <em> <pre> <code> <a href="" title="">

   Tagged with: , , , , , , ,