Solaris patch description

1. solaris patch Introduction 1.1 The types of patches and the file name of solaris patches are divided into two categories: Point patch and Cluster patch. A) Point Patch: This type of Patch is only a single Patch released for a certain problem or defect. The patches of solaris7, solaris8, and solairs9 are generally *. zip files.

1. solaris patch Introduction 1.1 The types of patches and the file name of solaris patches are divided into two categories: Point patch and Cluster patch. A) Point Patch: This type of Patch is only a single Patch released for a certain problem or defect. The patches of solaris7, solaris8, and solairs9 are generally *. zip files.

1. solarisPatchIntroduction
1.1PatchType and file name
SolarisPatchThere are two types: PointPatchThe other is Cluster.Patch.

A) PointPatchProgram:
This typePatchOnly a single release for a problem or defectPatchProgram, the patches of solaris7, solaris8, and solairs9 are generally * .zipfile solaris2.6is generally .tar.zor .tar.gz file, which has the following numbering method: GawLinux Alliance
Patch base code-revision num (for example, 110668-04)PatchBase code, which is laterPatchThe revision number. Both constitute thisPatchThe Patch-ID. For examplePatch, 110668 is the major version number, and 04 is the revision number. ThisPatchA new fix was made on the basis of 110668-03. One thing to note,PatchA seriesPatchAll are fixed for different problems in the/usr/sbin/in. telnetd file. After the release of 110668-04, sun will no longer providePatchSuch as 110668-03.

B) ClusterPatchProgram:
ClusterPatchJust a series of pointPatchAnd comes with an automatic installation program. ClusterPatchThe naming method is as follows:
Version_Recommended
For example, 9_x86_Recommended.zip is for Solaris 9 for X86.PatchSet.
8_Recommended.zip is for Solaris 8PatchSet.
Each ClusterPatchTer_readme file.PatchAnd installation methods or precautions.

1.2 aboutPatchSun maintains a Patch Reports for each version of solaris. This Patch Reports contains allPatch. Patch Reports are updated twice a month. You can obtain the following address:
Http://sunsolve.sun.com/pub-cgi/show.pl? Target = patches/patch-access & nav = patchpage
Sun also maintains a Sun Alert Patch Report, which is classified by product and updated at any time. From here, you can find the update documents of all sun products and their correspondingPatchOf course, it also includes the Sun Alert document of solaris, Patch ID, briefDescription. Sun Alert Patch Report can be obtained from:
Http://sunsolve.sun.com/pub-cgi/show.pl? Target = sunalert_patches
The corresponding solaris section can be obtained from the following link:
Http://sunsolve.sun.com/pub-cgi/show.pl? Target = sunalert_patches # The Solaris table is sorted by time. You can see from the Category table whether the problem is caused by a security defect fix or application optimization. II,PatchDownload GawLinux
ClusterPatchCan be downloaded from the following URL: http://sunsolve.sun.com/pub-cgi/show.pl? Target = patches/patch-access & nav = patchpage can also be downloaded using the FTP protocol. All clusters can be found in/pacthroot/clusters of sunsolve.sun.com.Patch. The downloaded file is a * _Recommended.zip file. The compressed file contains a CLUSTER_README file. Read this file before installation.
PointPatchBecause it is not easy to download and manage, you can use Sun Alert Patch Report or Patch Reports to viewPatchThe Patch ID and the corresponding Patch ID of the two documents. In addition, the Patch Finder feature provided by sun allows us to conveniently find this feature when we know the Patch ID.Patch, The connection is as follows:
Http://sunsolve.sun.com/pub-cgi/show.pl? Target = patches/patch-access & nav = patchpage
Similarly, you can use the ftp protocol to download the specified Patch from the/patchroot/all_unsigned directory of sunsolve.sun.com.
Sun recommends that all downloadedPatchPut them in the/var/tmp directory (this is also the common practice). This will not causePatchAny permission/ownership issues during installation.
Iii. solarisPatch3.1/var/sadm/patch directory. in the/var/sadm/patch directory, the installedPatch. For example: # ls/var/sadm/patch 107558-05 107594-04 107630-01 107663-01 107683-01 107696-01 107817-01 107582-01 107612-06 107640-03 is recommended make any changes to this directory, this directory cannot be installed or deleted after it is damagedPatch.

3.2 managing solarisPatch
Solaris provides two commands for management.Patch, Patchadd and patchrm. These two commands are provided starting with Solaris 2.6. In versions earlier than 2.6, eachPatchThe package contains an installpatch program and a backoutpatch program.Patch.
Install and decompressPatchProgram. Patchadd is installed by calling the pkgadd commandPatch. InstallPatchBefore, we needPatchDecompress the package to/var/tmp for installation. InstallPatchRun the following command:
# Cd/var/tmp
# Patchadd 110668-04 Checking installed patches...
Verifying sufficient filesystem capacity (dry run method) Installing patch packages...
If the current directory contains the 110668-04 directory, patchadd will installPatch.PatchAfter installation, the system will back up the original file to delete thisPatch. If you use the patchadd-d option to installPatch, The system will not back up the source file, which means you will not be able to delete thisPatch. Use the patchadd-p option to check installed patches, for example, GawLinux alliance.
# Patchadd-p
Patch: 106793-01 Obsoletes: Requires: Incompatibles:
Packages: SUNWhea
... Similarly, solaris provides another command to view installed patches:
# Showrev-p
Patch: 106793-01 Obsoletes: Requires: Incompatibles:
Packages: SUNWhea
...
Patchrm If You Want To uninstallPatchYou can use the patchrm command. This command resumes installation by calling pkgadd.PatchBefore file backup to uninstallPatch. You can use Patch-ID as the patchrm parameter to uninstall it.Patch: GawLinux Alliance
# Patchrm 106793-01
Checking installed packages and patches...
Backing out patch 106793-01...
Patch 106793-01 has been backed out.
Here we needDescriptionIn the following three cases,PatchIt cannot be uninstalled:
1) when installing the patch, run the patchadd-d command to specify that patchadd does not back up the updated files. The installed patch cannot be deleted.
2) Another patch requires this patch, that is, there is a dependence (correlation). If you must delete this patch, delete another patch first.
3) the patch to be deleted has been discarded by another update. For example, install 110668-04.PatchIf 110668-03 has been installed before, 110668-03 will be discarded by 110668-04, and 110668-03 will not be deleted.

3.3 ClusterPatchInstallation
ClusterPatchFor a singlePatchYou can run the./install_Cluster script to download and decompress the package.PatchSet installation. After you execute./install_Cluster, the script will check the patch_order file in the current directory, which indicates the Patch installation sequence../install_Cluster will install the patch in the order given by the patch_order file. If no patch_order file exists, it is assumed that all directories starting with 1 in the current directory are to be installed.PatchDirectory, and the order of these directories as the order of Install patches. Therefore, you can modify the patch_order file to determine whether to install or not install a Patch. GawLinux Alliance

3.4 precautions for Patch installation
Because files need to be updated during Patch installation, Solaris officially recommends installationPatchInstallation in single user mode. Some important servers may cause inconvenience, so you can complete Patch installation by stopping the service process in multi-user mode.
Not every Patch released by Sun must be installed. Therefore, read README carefully before installing the patch to determine whether to install thisPatch. In addition, somePatchIt is dependent and needs to be installed firstPatchTo complete thisPatchThe installation will be indicated in README. In short, installPatchWe strongly recommend that you read the corresponding README (each Patch provides a separate README file ).
3.5 problems during PATCH installation
InstallPatchDuring the process, some errors are often prompted. For example:
Installation of 123456-11 failed. Return code 2 through Return code we can know the error type. Note that Return code 2DescriptionThisPatchInstalled, Return code 8DescriptionThisPatchThe software to be repaired is not installed by the system. Therefore, 2 and 8 are error messages that can be ignored completely. Table belowDescriptionThe error types corresponding to each Return code.
Exit code Meaning
0 No error
1 Usage error
2 Attempt to apply a patch that's already been applied
3 valid tive UID is not root
4 Attempt to save original files failed
5 pkgadd failed
6 Patch is obsoleted
7 Invalid package directory
8 Attempting to patch a package that is not installed
9 Cannot access/usr/sbin/pkgadd (client problem)
10 Package validation errors
11 Error adding patch to root template
12 Patch script terminated due to signal
13 Symbolic link added in patch
14 not used 15 The prepatch script had a return code other than 0.
16 The postpatch script had a return code other than 0.