Hi -
I finally have a solution that I'm comfortable with.
Original question pertained to a failed dupatch install (pk#4) that left the
patches in an unknown state; i.e. -- dupatch said all patches were installed
but setld said that ~60 were not installed. The OS seemed ok but I didn't
want to take the machine live with basic OS and kernel patches not
installed.
Rob Brothers from gl-solutions (www.gl-solution.com) worked with Compaq to
determine how to straighten this out:
On the system as root cd /usr/.smdb.
ls OSFPAT*
mkdir temp
mv OSFPAT* to that temp directory
run dupatch, the system check part first, if that says all is well
run the
patch kit.....
I've done this and now all the patches are installed and everything is just
a-ok!
Thanks to everybody on the list who replied to my original question and to
those who helped me find a local Tru64 consulting resource (there are quite
a few outstanding ones around here -- I'll be glad to post the names of
those I contacted in the Boston, MA area if anybody is interested).
Andy
Original question:
===========
I applied Patch Kit #4 last week. I just issued a
setld -i|grep PAT|grep -v installed
and got back a number of items indicating to me that there are a number of
patches that are not installed. However, when I run dupatch for patch kit 4
I get a message:
All patches in /usr/du_patches/patch_kit/DIGITAL_UNIX_V4.0F/kit are
already installed.
How do I fix this? the setld command I issued above returns 60 rows (60
patches not installed). Do I have to install each one manually via setld?
This is a DS20E running 4.0F.
Received on Tue Sep 12 2000 - 15:23:38 NZST