Bernd, Sorry, I give "partial" answer and return to this tommorow.
> Is this feature "no need for ordering" already > included in the patchadd of Solaris 10 Update 3? It is two years there from Solaris 10 FCS. One of the most unnoticed but significant (IMHO) improvement of Solaris10. > > For our environment it's sufficient if patchadd > returns a non-zero return code if at least one patch > installation failed. If this is the case there should > be more information in the logfile about the reason > for the patch installation failure and maybe a > summary printed to STDERR. > > patchadd errors because a package is missing or > because a patch is already installed should be > ignored. > I think we have something 0 - OK, 1 - Total Failure and 2 - Some patches failed. But I should check soure code. And it produce a lot of output - someone even complained about it. > We still have Solaris 8 and Solaris 9 in place and we > must take care that the patch process is equal as > much as possible for all Solaris versions in > production. When the majority of our Solaris Boxes > are using Solaris 10 or newer it might be again an > option to redesign our patch process using more of > the new features of Solaris 10. > Good poin. I did not even think abuot such compatibility. > >>I can imagine something like - "report status of > this patch if we try to > >>install it with that other patches". Like > additional option specifying > >>patch which you are interested in. Pdo is so fast > that analyzing all > >>patches to report only one will take no time and > not a problem. > > ?? I mean that you directly specify PatchID which you are interested in. patchadd -a -Q 111222-01 -M /patches <patch list> and in result it will report exit code for 111222-01 so you may specify which patch you are interested in. For this I just do entier patch list check but give you back result for this one patch - pdo is so fast that difference between check for one patch and for all will be unnoticed. This message posted from opensolaris.org
