Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Weird Exit Status of shell script
Top Forums Shell Programming and Scripting Weird Exit Status of shell script Post 302810455 by fpmurphy on Tuesday 21st of May 2013 10:14:01 PM
Old 05-21-2013
It is due to the fact that you are using a pipeline.

To see the difference, change your code to:
Code:
#!/bin/bash

if [ $# -lt 1 ] ; then #Check there is enough command line parameters.
        exit 1
fi

while read i
do
        `[ -e $i ]`
        if [ $? != 0 ] ; then
             exit 1
        fi
done < $1

exit 0

By the way, your if expression would be better written as:
Code:
while read i
do
     if  [ ! -e $i ]
     then
         exit 1
     fi
done < $1

This User Gave Thanks to fpmurphy For This Post:
Ray Sun
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

checking exit status of a shell script

Hi, I have tried with the following code; if ;then echo "Failure." else echo "Success." fi to test the exit status of the test.ksh shell script. But whatever is the exit status of the test.ksh shell script Failure. is always printed. Please help. regards, Dipankar. (2 Replies)
Discussion started by: kdipankar
2 Replies

2. Programming

exit status running java classpath in unix shell

I have a java classpath running inside of a unix shell script. During my testing it will error with lines that show an example like this below. java.io.FileNotFoundException error at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:129), ... (2 Replies)
Discussion started by: mmcds
2 Replies

3. Shell Programming and Scripting

problem in exit status of the command in a shell script-FTP

Hi All, I have developed below script for FTP a file from unix machine to another machine. ftpToABC () { USER='xyz' PASSWD='abc' echo "open xx.yy.zbx.aaa user $USER $PASSWD binary echo "put $1 abc.txt" >> /home/tmp/ftp.$$ echo "quit" >> /home/tmp/ftp.$$ ftp -ivn <... (3 Replies)
Discussion started by: RSC1985
3 Replies

4. Shell Programming and Scripting

Need urgent help on exit status of the script

Guys, I am writing a script that executes a series of commands with a function like: _Command "ps -ef | grep java" _Command "vmstat" _Command "llll" Even if one of these commands fail, my script should exit with non-zero code i.e 16. If all commands are successful, my script should exit... (7 Replies)
Discussion started by: sriramperumalla
7 Replies

5. Shell Programming and Scripting

store last command exit status in variable in shell script

Hello All My req is to store the exit status of a command in shell variable I want to check whether the file has header or not The header will contain the string DATA_ACQ_CYC_CNTL_ID So I am running the command head -1 $i | grep DATA_ACQ_CYC_CNTL_ID Now I have to check if... (6 Replies)
Discussion started by: Pratik4891
6 Replies

6. Shell Programming and Scripting

exit status from the script is always 0

Hi , I have a bash script , which does the network configuration. Messages from this script are dumped on console as well as stored in a log file . This script is invoked from a C code using system call . The script returns different exit code , to indicate different error cases. The... (1 Reply)
Discussion started by: abhirai
1 Replies

7. Shell Programming and Scripting

Exit status of the ksh Script

Hi Im trying to write a script that will archive some file using java program.Below is the part of the script that I use and my problem is that the script always return with status 0.Below is part of my script(end part) purge.ksh echo "No of files before tar :... (4 Replies)
Discussion started by: saachinsiva
4 Replies

8. Shell Programming and Scripting

Exit status in the script

Hi all, I am trying to use a script (a.sh) which is calling another script(b.sh). And I want to use the exit code(set by me) of b.sh in a.sh. I am using this in b.sh #!/bin/sh <-- code --> if ; then exit 0 else exit 1 fiBut... (2 Replies)
Discussion started by: Raj999
2 Replies

9. Shell Programming and Scripting

Test with non-zero status does not exit shell

Hi there, I'm very used to use set -e to break my scripts if any command exits with a non-zero status. As a policy, I'm willingly expecting echo hello | grep a to break the script. The commands test 1 -eq $1 && echo hello exits with a non-zero status if $1 is not 1. BUT... It doesn't break... (2 Replies)
Discussion started by: chebarbudo
2 Replies

10. Shell Programming and Scripting

Inner script run and its exit status

Main Script #!/bin/ksh echo "Maimn script" ./clocal/www/web-data/WAS/WebSphere7/scripts/DealerLocator/Scripts/secondscript.ksh echo "$? = status" Sdecond Script #!/bin/ksh echo "In second SCript" exit 1 Output: Maimn script ./testmain.ksh:... (4 Replies)
Discussion started by: dineshaila
4 Replies

LEARN ABOUT LINUX

system

SYSTEM(3)						     Linux Programmer's Manual							 SYSTEM(3)

NAME

       system - execute a shell command

SYNOPSIS

       #include <stdlib.h>

       int system(const char *command);

DESCRIPTION

       system()  executes  a command specified in command by calling /bin/sh -c command, and returns after the command has been completed.  During
       execution of the command, SIGCHLD will be blocked, and SIGINT and SIGQUIT will be ignored.

RETURN VALUE

       The value returned is -1 on error (e.g.	fork(2) failed), and the return status of the command otherwise.  This latter return status is	in
       the  format  specified in wait(2).  Thus, the exit code of the command will be WEXITSTATUS(status).  In case /bin/sh could not be executed,
       the exit status will be that of a command that does exit(127).

       If the value of command is NULL, system() returns nonzero if the shell is available, and zero if not.

       system() does not affect the wait status of any other children.

CONFORMING TO

       C89, C99, POSIX.1-2001.

NOTES

       If the _XOPEN_SOURCE feature test macro is defined (before including any header files), then the macros	described  in  wait(2)	(WEXITSTA-
       TUS(), etc.) are made available when including <stdlib.h>.

       As  mentioned, system() ignores SIGINT and SIGQUIT.  This may make programs that call it from a loop uninterruptible, unless they take care
       themselves to check the exit status of the child.  E.g.

	   while (something) {
	       int ret = system("foo");

	       if (WIFSIGNALED(ret) &&
		   (WTERMSIG(ret) == SIGINT || WTERMSIG(ret) == SIGQUIT))
		       break;
	   }

       Do not use system() from a program with set-user-ID or set-group-ID privileges, because strange values for some environment variables might
       be  used  to subvert system integrity.  Use the exec(3) family of functions instead, but not execlp(3) or execvp(3).  system() will not, in
       fact, work properly from programs with set-user-ID or set-group-ID privileges on systems on which /bin/sh is bash version 2, since  bash  2
       drops privileges on startup.  (Debian uses a modified bash which does not do this when invoked as sh.)

       In versions of glibc before 2.1.3, the check for the availability of /bin/sh was not actually performed if command was NULL; instead it was
       always assumed to be available, and system() always returned 1 in this case.  Since glibc 2.1.3, this  check  is  performed  because,  even
       though  POSIX.1-2001  requires a conforming implementation to provide a shell, that shell may not be available or executable if the calling
       program has previously called chroot(2) (which is not specified by POSIX.1-2001).

       It is possible for the shell command to return 127, so that code is not a sure indication that the execve(2) call failed.

SEE ALSO

       sh(1), signal(2), wait(2), exec(3)

COLOPHON

       This page is part of release 3.27 of the Linux man-pages project.  A description of the project, and information about reporting bugs,  can
       be found at http://www.kernel.org/doc/man-pages/.

								    2010-09-10								 SYSTEM(3)
All times are GMT -4. The time now is 08:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy