> We must use a script very similar to Bernd's that applies each patch
> individually and captures the return code. At the end we tell the
> sysadmin if there was any error he should go back and check. And
> yes, we use the internal non documented return codes of the old
> patchadd to check if the error was a simple "package doesn't exist"
> or "patch already applied" ... Obviously we have changed our script
> to use -t on Solaris 10 as well.
I can do this for you. Actually I am doing this for you printing out at the end
of patchadd all results. Here I just extract states of the patches I collect
during dependency check
PDO_PATCHES_ALREADY_INSTALLED
PDO_PATCHES_ALREADY_REQUESTED
NO_PACKAGES_FOR_PATCHES
PDO_INCOMPATIBLE_PATCH_EXISTS,
PDO_INCOMPATIBLE_WITH_PATCH_TO_INSTALL,
PDO_INCOMPATIBLE_BY_EXISTED_PATCH,
PDO_INCOMPATIBLE_BY_PATCH_TO_INSTALL,
PDO_PATCH_HIGHER_REVISION_EXISTS,
PDO_PATCH_HIGHER_REVISION_INSTALL,
PDO_PATCH_HIGHER_REVISION_OBS,
PDO_PATCH_OBS_BY_EXISTED,
PDO_PATCH_OBS_BY_INSTALL,
PDO_PATCH_OBS_BY_OBS,
PDO_PATCH_PACKAGES_NOT_FOUND,
PDO_REQUIRED_PATCH_DOES_NOT_EXIST,
PDO_REQUIRED_PATCH_HAS_NO_REQUIRED,
PDO_REQUIRED_PATCH_INCOMPATIBLE,
PDO_REQUIRED_PATCH_HAS_NO_PACKAGES,
And all this is print out to standard output during patchadd.
And for zones I do additional print out.
In pdo.c it is all collected in special structure and attached to patch so I
can do any kind of summaries, any kind of "select" requests etc. I actually
thinking of printing it out in some kind of XML and let 3rd party tool do all
this selects and summaries. Also they can alarm sysadmin if needed...
So this is most likely exactly what your script doing but with in more details.
> I wouldn't mind changing over to 'patchadd -M <patch-dir> <our-list>'
> at all and let you do all the hard work! But we do like a summary at
> the end that lets us know about the patch errors that we need to go
> and look for (could also be solved by parsing friendly output). The
> exit code should reflect the difference between a "notice" (e.g.
> didn't add patch as the package it patches isn't installed - nice to
> report but that's about it), "warning" (e.g. couldn't add patch
> because a required patch is missing) and "errors" (tried to add patch
> but something went horribly wrong - we need the sysadmin to go and
> check). It should report the worst.
> I know our sysadmins would hardly ever check through the output of
> patchadd when adding 100+ patches to check if there was any error.
> As you say "And it produce a lot of output - someone even complained
> about it." Too much output currently leaves you blind to what really
> happened when trying to add all the patches.
> - mo
>
I may do any type of output for you. I have all information and really confused
on how to print it out. So I think we may discuss this here and came up with
something which satisfy most of you.
Clearly patchadd now doing what your scripts doing. And honestly you have your
scripts only because patchadd did not have real multipatching - you have to
compensate lack of development support from us. Now it is fixed (for 2 years)
and now patchadd may handle it but I personally do not have same field
experience as you are - I was sysadmin in small insurance company for about 6
months and have some idea what IT department usually doing, but that's it. Tell
me about you script behavior and let me make patchadd behave same way.
>
> btw, thanks for all your info you post to the list, glad I'm
> subscribed and see it all. Wouldn't it be better committed to a web
> page as permanent and maintainable documentation rather than hoping
> people might find it again trawling mailing list archives? Do you
> think "One of the most unnoticed but significant ... improvement"s
> will be noticed by a wider audience this way? Well, I'm happy, I get
> the info, I did notice it this way :)
I am not subscribed myself (can not handle regular mails) and use this:
http://www.opensolaris.org/jive/forum.jspa?forumID=107
I get used to participate different web forums and think that this is best
Internet instrument which combine wed server and mail discussions together. I
will not do webserver - until I give up some of recursive installation. So this
threads are best way for me and I will keep everything here as a single entry
point.
vassun
This message posted from opensolaris.org
