topic Re: Exit Script on failure? in Operating System - HP-UX

Exit Script on failure?

Duffs — Wed, 22 Jun 2005 05:31:01 GMT

Hi,

I have written sub script that sends (rcp's) a certain type of file to another server. If by any chance the line drops however this file will be put into an archive dir resulting in the file not being sent. Can anyone tell me how I can incorporate a err/exit code into my script so that if the rcp fails then the entire script will exit at that point peventing the file being archived and ensuring that it will get rcp'ed the next time it is run from the cron.

Dermot

Re: Exit Script on failure?

Devender Khatana — Wed, 22 Jun 2005 05:33:32 GMT

Hi,

Can you attach the script & the cron entry which is doing this?

Regards,
Devender

Re: Exit Script on failure?

Duffs — Wed, 22 Jun 2005 05:39:18 GMT

Please find the attached script.

This sub script is called as part of a larger script that is kicked off the cron every 5 mins.

Re: Exit Script on failure?

Devender Khatana — Wed, 22 Jun 2005 05:42:51 GMT

Hi,

Could not open the attachment. Please reattach.

Regards,
Devender

Re: Exit Script on failure?

Bharat Katkar — Wed, 22 Jun 2005 05:44:36 GMT

Hi Dermot,
This should work :

.....
rcp ....
var1=`echo $?`
if [ $var1 -ne 0 ]
then
exit
fi

Re: Exit Script on failure?

Muthukumar_5 — Wed, 22 Jun 2005 05:47:33 GMT

You can get return value from rcp command after it's execution as,

rcp :/tmp/test/*.sh /tmp/test/
if [[ $? -eq 0 ]]
then
echo "success"
...action..
else
echo "failure"
fi

hth.

Re: Exit Script on failure?

Duffs — Wed, 22 Jun 2005 06:15:19 GMT

These error messages only apply to the sub-script, they don't actually transfer to the main script therefore the program doesn't actually exit but continues excuting the remaining sub scripts instead of bombing out.

I really need to know how to transfer an error message from one script (this sub script) to another script (my main script).

Dermot

Re: Exit Script on failure?

Muthukumar_5 — Wed, 22 Jun 2005 06:32:58 GMT

I have read your script but with un-need codes more there.

#!/bin/ksh
# subscript.ksh
rcp server2:
if [[ $? -eq 0 ]]
then
echo "Success"
else
echo "failure"
exit 1
fi

exit 0

######################

#!/bin/ksh
#main.ksh
sh subscript.sh
if [[ $? -eq 0 ]]
then
echo "Subscript is successful"
else
echo "Subscript is failed"
exit 1
fi
exit 0
hth.

Re: Exit Script on failure?

Muthukumar_5 — Wed, 22 Jun 2005 06:36:36 GMT

You can also use global log file to log subscript informations.

#!/bin/ksh
#subscript.ksh
LOGFILE=/tmp/subscript.log
rcp ..
if [[ $? -eq 0 ]]
then
echo "success" > $LOGFILE
else
echo "failed" > $LOGFILE
fi

## Main script ###
#!/bin/ksh
#main.ksh
LOGFILE=/tmp/subscript.log
ksh subscript.ksh
if [[ -f $LOGFILE ]]
then
grep -q success $LOGFILE
if [[ $? -eq 0 ]]
then
echo "Subscript execution is success"
else
echo " ...failed"
fi
fi

hth.

Re: Exit Script on failure?

Duffs — Wed, 22 Jun 2005 06:46:40 GMT

Thanks a million, that did the trick, much appreciated!

Kind Regards,
Dermot

Re: Exit Script on failure?

Duffs — Wed, 22 Jun 2005 09:51:29 GMT

Hi,

As it turns out the above solution is only half the solution as it does not completely solve my problem. In the instance where there are no files to rcp, the script returns an error value of 1 thus bombing out instead of returning value zero and continuing to the next sub script.

Is there a way I can catalog the dir, i.e. run a 'ls' or 'read' on the dir and if there are no files present simply return a 0 and continue with the remainder of the script instead of exiting?

Dermot