Testing for exit status

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Want to get the exit status

Hi All, I am trying to create a zip file with all the txt files(these are in large number) in the current directory. I am able to do this operation sucessfully. After this i want to get the status of the tar command executed and do accordingly. When i am trying with the below code, the status...

2. Shell Programming and Scripting

Exit Status

I have a shell script (#!/bin/sh) that interacts with Appworx and Banner Admin. In my script I want to check the exit status of awrun before continuing. awrun can run for 10 seconds or it can run for over a minute. So my question is, will it go through my if statement before awrun may even be...

3. Shell Programming and Scripting

Exit status of grep

I am trying to get the exit status of grep and test a condition with it, But it does not seem to be working as expected since i am doing something wrong apparently as per grep help Exit status is 0 if match, 1 if no match, and 2 if trouble. My problem is something like this templine - a...

4. UNIX for Dummies Questions & Answers

$? = Exit status variable

hi, exit status variable $?, returns some digits. 0 ---> succes. 1..126 Failure (the program itself will decide what the numbers mean) 127 Command not found 128..254 The program did not exit normally. (E.g., it crashed, or received a signal) 255 Invalid exit code well, if $?...

5. Shell Programming and Scripting

Exit status

I'm preparing for exam and one of exams is to write own test command... I wonder if in unix is a command which just returns exit code you specify.. I know I can easily write a function like this: exStatus() { return $1 } -> my question is rather theoretical thank you!

6. Shell Programming and Scripting

How to get the exit status

Hi all, I'm running a program which return 1 upon success. But when encounters problem shell return 's '1' . How to differentiate between them the shell return value and script return value. Ex. function fn return '1' if executed successfully and '0' if failed. But when if shell encounters...

7. Shell Programming and Scripting

exit status for isql

I'm trying to write a script that will update a table in sysbase. If it's failed then I want to rerun it one more time before exiting the script (fail due to bad value such as trying to put a string into datetime field or bad connection to the database) Well my code below will always return...

8. Shell Programming and Scripting

Checking Exit Status

I hope one of you smart people out there can help me with what seems like a real simple questing but I can't quite figure out. In a script I am doing a cmp on two files. I am trying to check the exit status with an if statement but can't seem to figure out the syntax. If the exit status is 1 I...

9. Shell Programming and Scripting

Problem with exit status

Hi, Consider the output of the following commands: case1) ------- # ifconfig -a | grep "UP" | grep uplink0:1 # echo $? Output is: 0 case2 ------ # ifconfig -a | grep "UP" | grep uplink0:1; echo $? Output is: 1 In case2 we got the exit code as 1, which is the actual exit code....

10. Shell Programming and Scripting

exit status

i downloaded a text file from metalab.unc.edu called sh.txt and in this reference manual it refers to shell scripting exit status .. at the end of one of the examples that author gave an exit status of 127.. to what does a 127 exit status refer too and what is its purpose in the code. moxxx68

LEARN ABOUT BSD

return

exit(1)                                                            User Commands                                                           exit(1)

NAME

       exit, return, goto - shell built-in functions to enable the execution of the shell to advance beyond its sequence of steps

SYNOPSIS

   sh
       exit [n]

       return [n]

   csh
       exit [ ( expr )]

       goto label

   ksh
       *exit [n]

       *return [n]

DESCRIPTION

   sh
       exit  will  cause the calling shell or shell script to exit with the exit status specified by n. If n is omitted the exit status is that of
       the last command executed (an EOF will also cause the shell to exit.)

       return causes a function to exit with the return value specified by n. If n is omitted, the return status is that of the last command  exe-
       cuted.

   csh
       exit  will cause the calling shell or shell script to exit, either with the value of the status variable or with the value specified by the
       expression expr.

       The goto built-in uses a specified label as a search string amongst commands. The shell rewinds its input as much as possible and  searches
       for a line of the form label: possibly preceded by space or tab characters. Execution continues after the indicated line. It is an error to
       jump to a label that occurs between a while or for built-in command and its corresponding end.

   ksh
       exit will cause the calling shell or shell script to exit with the exit status specified by n. The value will be the  least  significant  8
       bits of the specified status. If n is omitted then the exit status is that of the last command executed. When    exit occurs when executing
       a trap, the last command refers to the command that executed before the trap was invoked. An end-of-file will also cause the shell to  exit
       except for a shell which has the ignoreeof option (See set below) turned on.

       return  causes a shell function or '.' script to return to the invoking script with the return status specified by n. The value will be the
       least significant 8 bits of the specified status.  If n is omitted then the return status is that of the last command executed.  If  return
       is invoked while not in a function or a '.' script, then it is the same as an exit.

       On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:

       1.  Variable assignment lists preceding the command remain in effect when the command completes.

       2.  I/O redirections are processed after variable assignments.

       3.  Errors cause a script that contains them to abort.

       4.  Words,  following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
           able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation  are  not
           performed.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE         |      ATTRIBUTE VALUE        |
       |Availability                 |SUNWcsu                      |
       +-----------------------------+-----------------------------+

SEE ALSO

       break(1), csh(1), ksh(1), sh(1), attributes(5)

SunOS 5.10                                                          15 Apr 1994                                                            exit(1)

UNIX for Dummies Questions & Answers