How to get exit status codes in bash from Perl? Post: 87593

10 More Discussions You Might Find Interesting

1. Programming

exit codes

Where can a locate a list of Unix exit codes? thank you, Donna

2. UNIX for Dummies Questions & Answers

Where can I find a list of exit codes? (Exit code 64)

I'm receiving an exit code 64 in our batch scheduler (BMC product control-m) executing a PERL script on UX-HP. Can you tell me where I can find a list of exit codes and their meaning. I'm assuming the exit code is from the Unix operating system not PERL.

3. Shell Programming and Scripting

Catching all Exit Codes

I have a Unix Script that has several exit in the middle. each returning seperate exit codes. I have to catch all the exit's and perform an operation say "Mail the status code" before the actual code completes. How can i do this in KSH ?

4. UNIX for Advanced & Expert Users

Explanation for the exit codes 2

Hi, Can anyone give me the explanation for the exit codes 1 and 2 returned from Korn shell. Thanks in advance.

5. Shell Programming and Scripting

bash awk codes to perl

Hi, I am interesting in writing the following bash codes into perl My script is simple take field 2 in /etc/passwd and put into an array #!/bin/bash PASSWD_FILE=/etc/passwd A=(`awk -F: ' { print $2 }' $PASSWD_FILE `) Can someone give me equivalent codes in perl ?

6. Shell Programming and Scripting

Exit Codes

Good Morning All.. I was wondering about getting exit codes of a command in a shell script. I'm trying to run uvscan (McAfee command line scanner) and I want to have the log file say why, if at all, the process failed/exited. Something to the extent of If ; then echo "This is why it...

7. Linux

Exit codes

I am trying to run this SH on Linux and getting error at IF condition. I want to read the EXIT code and send the failure or success message. Please help me on this. This worked when i was running on Solaris. #!/bin/bash $ORACLE_HOME/bin/sqlplus abc/xyz@qwe @/home/test.sql if ;...

8. Shell Programming and Scripting

Bash Shell Script Exit Codes

Here is my daily stupid question: How can I tell a script to only execute if the other scripts exits successfully? So "script A" executes and it executes successfully (0),then "script B" will run or else "script A "executes and it exits unsucessfully (1) then "script B" will read return...

9. Shell Programming and Scripting

Perl Question Grep and exit status

Im being forced to write in perl. I prefer KSH or Expect, so I suppose its time to become more fluent with perl. I have the following problem. I want to loop through Filea and check that each line in Filea is resident in Fileb. Filea contents two four six eight houseboat Fileb...

10. Shell Programming and Scripting

Ignore exit status for #!/bin/bash -e

I have a file /u/setuplink.txt more setuplink.txt ln -s /u/force.sh stopf.sh ln -s /u/tnohup.sh tnohup.sh ln -s /u/quick.sh startquick.sh more runstat.sh #!/bin/bash -e echo "START" /u/setuplink.txt echo "END" i wish to exit the runstat.sh for any errors except if the link...

LEARN ABOUT POSIX

libbash

LIBBASH(7)							  libbash Manual							LIBBASH(7)

NAME

     libbash -- A bash shared libraries package.

DESCRIPTION

     libbash  is  a package that enables bash dynamic-like shared libraries. Actually its a tool for managing bash scripts whose functions you may
     want to load and use in scripts of your own.

     It contains a 'dynamic loader' for the shared libraries ( ldbash(1)), a configuration tool (ldbashconfig(8)), and some libraries.

     Using ldbash(1) you are able to load loadable bash libraries, such as getopts(1) and hashstash(1).  A bash shared library that can be  loaded
     using
     ldbash(1) must answer 4 requirments:

     1.     It must be installed in $LIBBASH_PREFIX/lib/bash (default is /usr/lib/bash).

     2.     It must contain a line that begins with '#EXPORT='.  That line will contain (after the '=') a list of functions that the library
	    exports.  I.e. all the function that will be usable after loading that library will be listed in that line.

     3.     It must contain a line that begins with '#REQUIRE='.  That line will contain (after the '=') a list of bash libraries that are
	    required for our library.  I.e. every bash library that is in use in our bash library must be listed there.

     4.     The library must be listed (For more information, see ldbashconfig(8)).

   Basic guidelines for writing library of your own:
     1.     Be aware, that your library will be actually sourced. So, basically, it should contain (i.e define) only functions.

     2.     Try to declare all variables intended for internal use as local.

     3.     Global variables and functions that are intended for internal use (i.e are not defined in '#EXPORT=') should begin with:
		  __<library_name>_
	    For example, internal function myfoosort of hashstash library should be named as
		  __hashstash_myfoosort
	    This helps to avoid conflicts in global name space when using libraries that come from different vendors.

     4.     See html manual for full version of this guide.

AUTHORS

     Hai Zaar <haizaar@haizaar.com>
     Gil Ran <ril@ran4.net>

SEE ALSO

     ldbash(1), ldbashconfig(8), getopts(1), hashstash(1) colors(1) messages(1) urlcoding(1) locks(1)

Linux								       Epoch								     Linux

10 More Discussions You Might Find Interesting

1. Programming

exit codes

Discussion started by: donna carter

2. UNIX for Dummies Questions & Answers

Where can I find a list of exit codes? (Exit code 64)

Discussion started by: jkuchar747

3. Shell Programming and Scripting

Catching all Exit Codes

Discussion started by: Sivaswami J

4. UNIX for Advanced & Expert Users

Explanation for the exit codes 2

Discussion started by: sesedada