Shell Programming and Scripting

Can you please let me know how can i verify /check inside the script if the below to package installation commands are successful or if they failed for any reasons?

1. pkgadd -a $INSTP/install/dadmin -d $INSTP/install/apachesrv.pkg
2. pkgadd -a $INSTP/install/dadmin -d $INSTP/install/apachesrv.pkg>/tmp/install.log

Code:

uname -a
SunOS mymac 5.11 11.2 sun4v sparc sun4v

You do it with pkgadd the same way you do it with every other command... You check the man page for the utility in question to see what exit code it produces when it succeeds. You run the command. You check the exit code after the command completes. And, if the exit code matches the exit code listed on the man page for that utility for successful completion, then you know the command succeeded; otherwise, it failed.

As with about 99.44% of utilities, pkgadd exits with exit code 0 if it completed successfully. Of course, the way you check the exit status varies depending on the shell you use (and you haven't bothered to tell us what shell you use). If we make the wild assumption that you're using sh, ksh, bash, or /usr/xpg4/bin/sh (or another shell based on Bourne shell syntax), you could try something like:

Code:

pkgadd -a $INSTP/install/dadmin -d $INSTP/install/apachesrv.pkg>/tmp/install.log
ec=$?
if [ $ec -eq 0 ]
then	echo 'pkgadd succeeded'
else	echo "pkgadd failed as indicated by diagnostics above and exited with exit code $ec"
fi
exit $ec

Wouldn't pkgadd -a $INSTP/install/dadmin -d $INSTP/install/apachesrv.pkg>/tmp/install.log
always succeed even if pkgadd fails becoz of the redirection >/tmp/install.log being successful ?

If this would be the case UNIX would be VERY wrong - and, in fact, it isn't. You probably confuse that with a pipe (cmd1 | cmd2 | cmd3) where you get only one exit code for all the commands.

@Don:

Its 99.43978210653% +/- one epsilon - roundabout. ;-))

I hope this helps.

bakunin

Good question. No, because a redirection is not a separate command. In the case of a simple command it is considered part of the simple command..

Shell Command Language: Simple Commands

So the return code reflects whether the simple command as a whole succeeded or not...

Shell Command Language: Exit Status for Commands

So, #!/bin/bash -e will exit the script even if pkgadd fails in the below statement ?

Code:

pkgadd -a $INSTP/install/dadmin -d $INSTP/install/apachesrv.pkg>/tmp/install.log

Yes.

And, you know that you can easily test this out with the script:

Code:

#!/bin/bash -e
echo before
false > junk
echo after

which if you save this in a file, make it executable, and run it will print before, create an empty file named junk, and exit without printing after.