[pca] trying unsuccesfully to run pca on a jumpstart finishscript

[Pierre-Yves.Thillier at infineon.com]

It seems that it's because of the naming resolution which is not done...
See below :
Resolving server.domain... failed: node name or service name not known.
Failed
Trying http://sunsolve.sun.com/patchdiag.xref (1/1) /a/usr/sfw/bin/wget "http://sunsolve.sun.com/patchdiag.xref" -O /a/tmp/patchdiag.xref
--15:26:32--  http://sunsolve.sun.com/patchdiag.xref
           => `/a/tmp/patchdiag.xref'
Resolving sunsolve.sun.com... failed: node name or service name not known.

I put the IP of my local pca proxy and it worked...

Fyi, the machine is installed with all the jumpstart informations taken from a Microsoft DHCP server and now I remember that the DNS informations are not well forwarded to the machine during the installation process...

Thanks for your help !

Pierre-Yves
-----Original Message-----
From: pca-bounces at lists.univie.ac.at [mailto:pca-bounces at lists.univie.ac.at] On Behalf Of Martin Paul
Sent: Thursday, December 18, 2008 3:43 PM
To: PCA (Patch Check Advanced) Discussion
Subject: Re: [pca] trying unsuccesfully to run pca on a jumpstart finishscript


> In Solaris 10, the wget includes SSL support, so it needs the SSL
> libraries under /usr/sfw/lib ($BASE/usr/sfw/lib in your example).  These
> libraries are not normally included on the jumpstart minimal OS from my
> experience, though I haven't looked at U6.

I think I once used a non-SSL version of wget, as you say, for that very
reason, but at least in recent releases of Solaris 10 (just checked
8/07) the SSL libraries in /usr/sfw/lib do exist in the miniroot booted
during jumpstart. One could probably simply use /usr/sfw/bin/wget nowadays.

Martin.