telnet closed in middle of patch install ..

[someone_4]

Hey everyone
I was in the middle of doing my first SD-UX patch upgrade. I was doing it via telnet
running
swinstall -s /cdrom
/cdrom being where i mounted the cd. The session got closed. So I logged back in to try to start over but it was telling me that the /cdrom was in use. So I do
ps -ef|grep swagent
I saw the proccess was still running.
So I killed it. Well now I restarted my upgrade. My question is .. was that the rigt way to do this? Or should I have done it another way? Should I cancel my upgrade and do something else?

Richard

[A. Clay Stephenson · Accepted solution]

Hi Richard:

You didn't do badly and probably about as well as possible. While this isn't always possible, it's really a good idea to install only from the console and especially for the General Release, HRCR's, or QualityPacks - the large patch bundles.

It is fine to use the GUI version or character version via telnet on most patchsets but there are some exceptions. Make sure that you read the Special Instructions section very carefully.

For the large patchset, running swinstall from the console minimizes the chances of connection errors.

Clay

[James R. Ferguson]

Hi Richard:

You were probably only in the beginnings of the analysis phase, so no harm, and no special handling required. You can view your /var/adm/sw/swinstall.log for more details.

When doing SD functions I like to run with the '-x rpc_binding_info=ncadg_ip_udp:[2121]' option (see 'man swinstall'). This is quite useful if you have Glance/Measureware running when you do the 'swinstall'. Without the option, and with the aforementioned running, 'swinstall' has been known to hang.

Regards!

...JRF...

[Santosh Nair_1]

If you're just doing the SD-UX patch, then you should be able to kill the swinstall session and restart swagentd and finally re-install the patch.

-Santosh