> If it's not documented in the man pages, then it's not supported. > Relying on internal implementation details isn't recommended.
Maybe, but because there is *no* documented method to check if a patch can be applied to a system before starting patchadd it's the only method I know to distinguish between expected errors and not expected errors while running patchadd in a script.. If you need to patch 100+ Solaris systems you can not do this manually - you need an automatic solution. regards Bernd PS: I filed a bug request to add the return codes to the man pages. -------- Original-Nachricht -------- Datum: Tue, 24 Oct 2006 09:43:15 -0400 Von: James Carlson <james.d.carlson at sun.com> An: Bernd Schemmer <Bernd.Schemmer at gmx.de> Betreff: Re: [install-discuss] Re: patchadd behaviour in Solaris 10 > Bernd Schemmer writes: > > > EXIT STATUS > > > The following exit values are returned: > > > 0 Successful completion. > > > >0 An error occurred. > > > > There's a list of return codes for patchadd that we use to > > distinguish between expected return codes and unexpected return > > code. This method worked fine for Solaris 8 and 9 and it should also > > work for Solaris 10 . > > If it's not documented in the man pages, then it's not supported. > Relying on internal implementation details isn't recommended. > > -- > James Carlson, KISS Network <james.d.carlson at sun.com> > Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 > MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 -- Bernd Schemmer Stalburgstr. 14 60318 Frankfurt Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal f?r Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
