[pca] Understanding --fromfiles
Martin Paul
martin at par.univie.ac.at
Fri Nov 13 11:18:10 CET 2009
Mauricio Tavares wrote:
> Now if I could make it tell me whether I am not allowed to download a
> patch (as opposite of it not being available) instead of just saying
>
> Trying https://sunsolve.sun.com/ (1/1)
> Failed
> Failed (patch not found)
I made up my mind, as some more details on failed patch downloads
definitely would be nice. It will also make support easier, as I won't
have to ask for debug output anymore in certain cases.
So the current development version of pca analyzes output from wget,
looks for errors, and displays them on failed donwloads of any file.
Example:
Looking for 142675-01 (1/1)
Trying https://sunsolve.sun.com/ (1/1)
Failed (Error 403: Forbidden)
...
I've also added a table of known errors to pca's documentation under
"DOWNLOAD ERRORS":
$ pca --man
...
DOWNLOAD ERRORS
If downloads of patches, patch READMEs or the patchdiag.xref
file fail, the displayed error might help to diagnose the
problem:
Unauthorized (401)
The user/passwd you provided is not correct.
Forbidden (403)
The user/passwd is correct, but the SOA is not connected
to a support contract, which is needed for the requested
file.
Not Found (404)
The requested file does not exist on SunSolve.
Server Error (500)
The SunSolve server is in a bad state. Retry later.
I just hope that both wget's output format and SunSolve's HTTP replies
won't change to often, forcing me to adapt my code. I tried to keep it
as generic as possible.
Martin.
More information about the pca
mailing list