Re: [pca] pca.sh exit code status
On 02/09/2012 03:50 AM, Martin Paul wrote:
> Chris Gibson wrote:
>> Should it not show an exit of 1? Also I would I exclude the exit status
>> of 3, 4 and 5 as we are patching ABE's and don't care about the reboot
>> notification.
>
> I know, PCA's exit values are from perfect. The problem is that the
> requirements of the users are quite different, and it seems to be
> impossible to express all the demanded information in a single
> numerical value. So as I couldn't find a solution which would please
> everybody, I didn't put much effort into this.
>
> In your case the best alternative would be to look for the "Download
> Summary" and "Install Summary" lines in PCA's output in your wrapper
> script. There you can get detailed information about all patch
> downloads and installations, separated into successful/skipped/failed
> patches.
>
> Hope that helps,
>
> Martin.
>
I added these 2 lines at line 338 in the current version. It exits with
1 if failed to download or failed to install is greater than 0. Someone
else might find this useful.
if ($c{faildl} > 0 || $c{failinst} > 0){
$xval || ($xval=1)}
Re: [pca] pca.sh exit code status
Chris Gibson wrote: Should it not show an exit of 1? Also I would I exclude the exit status of 3, 4 and 5 as we are patching ABE's and don't care about the reboot notification. I know, PCA's exit values are from perfect. The problem is that the requirements of the users are quite different, and it seems to be impossible to express all the demanded information in a single numerical value. So as I couldn't find a solution which would please everybody, I didn't put much effort into this. In your case the best alternative would be to look for the "Download Summary" and "Install Summary" lines in PCA's output in your wrapper script. There you can get detailed information about all patch downloads and installations, separated into successful/skipped/failed patches. Hope that helps, Martin.
[pca] pca.sh exit code status
We have been using pca.sh for a few years now. However we have always had eyes watching the patching process, doing a pretend first, fixing any skipped or failed, then an actual patch. We are now automating this. I am testing this on a test box and during a pretend, I set it up so I would fail the download portion. When I ran pca.sh on the CLI and it showed 80 failed, I then checked the exit status and it shows 0 Should it not show an exit of 1? Also I would I exclude the exit status of 3, 4 and 5 as we are patching ABE's and don't care about the reboot notification.
