[pca] PCA return codes
Finestead, Eric D [IT]
eric.d.finestead at sprint.com
Tue Oct 7 18:07:43 CEST 2008
While the bit return codes are interesting, I suspect that it's a little too complicated. For my wrapper script the only conditions I test for are:
Error (check logs).
Installed patches that recommend or require a reboot. (Done, reconfigure reboot and send email saying it's done.)
Did not finish installing patches because it hit a reboot immediately patch. (Reconfigure reboot and restart patching.)
Successful. (Didn't require a final reboot. Send email saying it's done.)
My thought is that other conditions (such as download failed, general error) aren't going to be handled by the wrapper script. You'll have to consult the logs to fix them anyway, so while it would be nice to have a more helpful return code than "check logs" it's really not necessary.
-Eric
________________________________
From: pca-bounces at lists.univie.ac.at [mailto:pca-bounces at lists.univie.ac.at] On Behalf Of Fred Chagnon
Sent: Tuesday, September 16, 2008 9:27 AM
To: PCA (Patch Check Advanced) Discussion
Subject: [pca] PCA return codes
In my wrapper script for pca, I would like to be able to determine if pca finished patching completely, or if it finished prematurely, perhaps due to a patch that required an immediate reconfigure reboot. Does pca have different return codes for these situations? Where can I see a list of possible exit situations?
Thanks.
Fred
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.univie.ac.at/mailman/private/pca/attachments/20081007/1f5cbd20/attachment-0001.html
More information about the pca
mailing list