Thanks for all the replies. But the correct answer came from
Kevin Partin who wrote:
I had the same problem yesterday. From Compaq
As a workaround try this:
There is an environment variable that needs to be set to 1 to force your
/usr/local/patch_kit/dupatch to load the new patch tools if you are
having problems.
To set the variable for ksh #export UPDATE_DUPATCH=1
Then rerun /usr/local/patch_kit/dupatch and the screen will display that
the new patch tools are being loaded.
When finished unset the variable or set it to 0 which is default.
This worked fine. My The only comment is that it was necessary to
unset this variable after the first time because setting it to 0
resulted in the same behavior as setting it to 1, i.e. the new patch
tools were loaded again.
Peter Stern
Original message below.
> I recently upgraded a system from Tru64 v4.0e to v4.0f and
> immmediately installed the lates patch kit (#4). Now when I
> try to run dupatch, it asks me to enter the path to the top of the
> patch distribution, and after I do that it states:
> dupatch:
> Patch tools need to be installed on your system. As the super-user
> (root), please invoke dupatch without command line arguments first.
>
> Of course, I DID invoke dupatch without command line arguments.
>
> I thought that the patch installation automatically installed the patch
> tools and indeed if I try to do:
> setld -l patch_tools
> I get:
> setld: All subsets on the kit are already installed
>
> Any ideas of what I am doing wrong here?
Received on Sun Jul 23 2000 - 06:45:18 NZST