Catching errors Post: 302300562

Sponsored Content

Top Forums Shell Programming and Scripting Catching errors Post 302300562 by GoldenEye4ever on Tuesday 24th of March 2009 12:09:30 PM

03-24-2009

Registered User

Catching errors

Hi,

I'm writing a scheduling script which will co-ordinate the launching of scripts.
This script is scheduling based on an input file, and launches the appropriate scripts at the right times.

The only issue I'm having is:
- if a script dies, or even has a syntax error, I want to catch that.
- this is needed as the scheduler script will have to put a hold on that script until it is fixed.

Here's what I have:

Code:

...
if [ "${beforeRunScript}" == "TRUE" ]; then
    if [ -f "${additionalScriptsPath}/before_${workerScript}.sh" ]; then
        echo "  ********************************"
        echo "  * START: \"Before Run\" script *"
        echo "  ********************************"
        $ . "${additionalScriptsPath}/before_${workerScript}.sh"
        errorCode=$?
        if [ ! "${errorCode}" == "0" ]; then
            echo `addToErrorQueue "${processName}" "${workerScript}" "${errorCode}" "Before-Run script has failed. A hold has been put on the process until it is fixed."`
            keepGoing=FALSE
        fi
        echo "  *******************************"
        echo "  * DONE: \"Before Run\" script *"
        echo "  *******************************"
    fi
fi
...

beforeRunScript is just a flag deciding whether or not the file is needed.
additionalScriptsPath is just the path where the script to be executed resides.
workerScript is just part of the name of the script to be launched.

When I run this code, I get:

Code:

...
********************************
* START: "Before Run" script *
********************************
./chk_master_script.sh[465]: $:  not found
*******************************
* DONE: "Before Run" script *
*******************************
...

If I run this code without the $ prior to the . (dot), when calling the script, the code works fine, but if errors exist in the called script, they're not caught by this scheduler script.

Also, the script being run must have access to all variables in this scheduler script, that's why I'm calling the script with the . (dot).

Any help would be great.

GoldenEye4ever

View Public Profile for GoldenEye4ever

Find all posts by GoldenEye4ever

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

catching interrupts

hey i have been facing a problem,can you tell me if we can catch ctrl d in unix i have tried and sucessfully catched and disabled ctrl-c and ctrl -z but am not sure if we can do the same for CTRL-D, so got any clue mail on he forum or ...i mean c programming in Unix thats what i am working on

2. Programming

Catching signal and piping

Hi, Recently I was reading some c coding by some colleagues and I noticed that the above trend. They will create a pipe for the process then they will use the standard signal handler to capture a particular signal and write that signal to the pipe. On the other end, the process will read the...

3. UNIX for Dummies Questions & Answers

Awk- catching the last two chars

Can anyone explain to me how to get the last two chars' from each row of Column (each row being variable in length) using awk, some of the lines will be blank, I'll be running a paste after awking. So I need to keep the blanks where they are..so I can paste back all columns in the correct order ...

4. 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 ?

5. Shell Programming and Scripting

catching some errors

I need to find a way to keep a running tally of how many times events or actions occur. Say if a user is prompted to make inputs of 1 or 2, I want it to keep track of how many times 1 was entered, and how many times 2 was entered. Thanks for your help

6. Programming

Signal catching

Hi! I want to catch all signals that my program receives print their name and then execute the default handler. Can you help me on that? I've tried the following code: #include <stdio.h> #include <unistd.h> #include <signal.h> void (*hnd)(int i); char signals = { "SIGHUP",...

7. Programming

popen catching output and errors

I have code which at the moment only catches the command/program output if the program runs correctly, which is a small problem as I would like to capture everything from stdout inclusive of errors FILE *fp; fp = popen(command.c_str(), "r"); while(fgets(cbuf, 1024, fp) != NULL){ .....do stuff...

8. Shell Programming and Scripting

Catching error in sftp

Hi All Experts, I have a script which logs to the server via sftp connection with below code :- user_name@sftp_server.com and the connection is going smooth. My requirement is to place file in sftp_server in some path. and if path doesn't exist or the file is not put successfully I...

9. Solaris

BSM not catching creat64

Solaris 9 system: I'm trying to get BSM to record to the point where additional files being put into /etc/opt/csw/sudoers.d will be recorded but thus far all I'm able to get are when files are deleted (via unlink). I've even tried auditing based on the "all" audit flag temporarily (thinking I...

LEARN ABOUT SUSE

installsieve

INSTALLSIEVE(1) 					      General Commands Manual						   INSTALLSIEVE(1)

 *

NAME

       installsieve - user utility for managing sieve scripts

SYNOPSIS

       installsieve

DESCRIPTION

       installsieve is a utility that allows users to manage their sieve scripts kept on the server.

OPTIONS

       -v <name> View script with the given name. The script if retrieved sucessfully is output to standard output.

       -l  List  all  of  the scripts currently on the server. If one of the scripts is active a arrow is printed indicating that it is the active
       script.

       -p <port> Port to connect to. If left off this defaults to "sieve" as defined in /etc/services.

       -i <file> Install a file onto the server. If a script with the same name already exists on the server it is overwritten.  Upon  sucessfully
       putting	the  script on the server the script is set active. If <file> has the extension .script it is chopped when put on the server since
       sieve names may not contain a '.'.

       -a <name> Set <name> as the active script. The list of available names can be obtained from the '-l' option..

       -d <name> Delete the sieve script on the server with <name>.

       -m <mechanism> Force installsieve to use <mechanism> for authentication. If not specified the strongest authentication mechanism is chosen.

       -g <name> Get the sieve script with <name> and save it to disk with a ".script" extension. If a file with that name already  exists  it	is
       overwritten.

       -u <user> Userid/Authname to use for authentication; by default, the current user.

CMU
								   Project Cyrus						   INSTALLSIEVE(1)