Installation Bugs

install_mu Does Not Function Correctly When Starting It Using sh 4108278

Because of problems regarding the interactions between sh(1) and ksh(1), the install_mu utility may fail to install certain patches correctly whenever you start it using the following command from the command line or from an administrative script:

# /bin/sh ./install_mu arguments

Workaround: Execute install_mu from the command line or from an administrative script as follows:

# ./install_mu arguments

install_mu Leaves Files in the /tmp Directory 4108278

install_mu leaves files and working directories in /tmp. The files and directories could cause /tmp to become full, potentially leading to system problems. Files and directories left in /tmp are of the form install* and SUNW*.

Workaround: After install_mu has completed execution, check /tmp for files and directories named install* and SUNW*. If the files were created recently by root, remove them. Or, if the MU was applied to a stand alone machine or server, reboot the system.

Patchadd Displays an Error That It Is Terminating

One of the following benign messages may be displayed by install_mu:

One or more patch packages included in
XXXXXX-YY are not installed on this system.

Patchadd is terminating.

Or:

Installation of XXXXXX-YY failed:
  Attempting to patch a package that is not installed.

These messages indicate that patchadd could not find on your system any of the packages that it intended to patch, so it skipped the indicated patch.

The message is displayed when patchadd notices a discrepancy installing a patch of one architecture onto a system with a different architecture (for example, a sun4u patch on a sun4c system.)

This may also be the result of one or more packages being missing from the system. The package may have been removed by the administrator, or never installed, as in the case of installing a cluster smaller than the Entire Distribution. This is common with diskless clients and AutoClients.

Workaround: Ignore the message.