>> $ /dss/bin/pca --version >> pca 20091030-01 >> $ /support/bin/pca --getxref --wget=/usr/local/bin --xrefdir=/tmp > >Are these two copies of pca? I assume that the version is the same?
My bad when creating the email. Both point to identical copy of pca script (one is actually symbolic link to the other). >Are both tests with and without --debug running on the same machine, >under the same user? Yes, identical. >The failure could be caused by a missing proxy server setting, but it >would then fail independent of --debug set or not. Are you setting the >proxy in a pca configuration file, in a wgetrc or via the http_proxy >environment variable? Outbound proxy is defined via .wgetrc file: $ cat ~/.wgetrc #verbose = on http_proxy = http://myproxy.mydomain.com:80 https_proxy = http://myproxy.mydomain.com:80 $ My pca.conf file (in same dir as pca script): # Sun Online Account user=<my Sun userid> passwd=<my Sun password> # Other patchdir=/export/home/patch/patches xrefdir=/export/home/patch/pca dltries=10 >To get more information, try wget directly, e.g.: > > /usr/local/bin/wget --no-check-certificate \ > https://sunsolve.sun.com/pdownload.do?target=patchdiag.xref"; \ > -O patchdiag.xref The above works just fine. >Also, while running the failing pca, try to run "ps" repeatedly in a >second terminal window to catch the exact wget command it runs (or use >"truss" for the same purpose) and compare it to the one when run with >--debug. Then try that command on the command line again and show us the >output. Using truss and "--debug" with my command line (i.e. a success), I can see the following executed: /usr/local/bin/wget "https://sunsolve.sun.com/pdownload.do?target=patchdiag.xref"; --ca-certificate=/dss/bin/pca -O /tmp/patchdiag.xref Using truss without "--debug" with my command line (i.e. a failure), I see no attempt at wget execution. Thanks, Lee
