SUMMARY: return codes of patchadd

From: Bernt Christandl <beb_at_MPA-Garching.MPG.DE>
Date: Mon Dec 15 2003 - 02:32:35 EST
Dear managers,

thank you all very much for your help!

The answers were like this from 
"Adrian Phipps (AC)" <PhippsAC"at"telkom.co.za> or
Frank Smith <fsmith"at"hoovers.com>:

> Don't know how current this is, but here's the  list I saved
> (my notes say INFODOC ID:  17973, but I'm not sure):

>  PATCH EXIT CODES, taken from an installpatch script with the date of:

>  # @(#) installpatch 6.9 98/10/09 SMI

>  # Exit Codes:
>  # 0 No error
>  # 1 Usage error
>  # 2 Attempt to apply a patch that's already been applied
>  # 3 Effective UID is not root
>  # 4 Attempt to save original files failed
>  # 5 pkgadd failed
>  # 6 Patch is obsoleted
>  # 7 Invalid package directory
>  # 8 Attempting to patch a package that is not installed
>  # 9 Cannot access /usr/sbin/pkgadd (client problem)
>  # 10 Package validation errors
>  # 11 Error adding patch to root template
>  # 12 Patch script terminated due to signal
>  # 13 Symbolic link included in patch
>  # 14 NOT USED
>  # 15 The prepatch script had a return code other than 0.
>  # 16 The postpatch script had a return code other than 0.
>  # 17 Mismatch of the -d option between a
>       previous patch # install and the current one.
>  # 18 Not enough space in the file systems that are targets # of the
>      patch.
>  # 19 $SOFTINFO/INST_RELEASE file not found
>  # 20 A direct instance patch was required but not found
>  # 21 The required patches have not been installed on the manager
>  # 22 A progressive instance patch was required but not found
>  # 23 A restricted patch is already applied to the package
>  # 24 An incompatible patch is applied
>  # 25 A required patch is not applied
>  # 26 The user specified backout data can't be found
>  # 27 The relative directory supplied can't be found
>  # 28 A pkginfo file is corrupt or missing
>  # 29 Bad patch ID format
>  # 30 Dryrun failure(s)
>  # 31 Path given for -C option is invalid
>  # 32 Must be running Solaris 2.6 or greater
>  # 33 Bad formatted patch file or patch file not found
>  # 34 The appropriate kernel jumbo patch needs to be installed


And my *real* problem was, that i managed in the hurry to patch
several machines at the same time, to try to apply 8Recommended
to a Solaris-7 machine... Now i have tested, that this will not hurt :)

With best regards,

Bernt Christandl

--------------------------------
My original question:

Dear managers,

i'm sorry if this should be in the FAQs...

This morning i'm trying to install the recommended and security
patches as many times before and i've got "new-to-me" error-codes
from the install-cluster script, which i cannot find in the manpage
of patchadd.

Could someone please point me to the right place where i can find
the "link" between return code number and the meaning of it?

I believe i remember that "2" means, "patch installation fails,
because it is already installed and "8", "patch istallation fails,
because the original package itself is not installed", 
but what does "5" and "25" means?

Thank you very much!

Bernt Christandl
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Mon Dec 15 02:32:23 2003

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:25 EST