M)Name. | Synopsis. Description. | Options. Operands. | KEYSTORE LOCATIONS. KEYSTORE AND CERTIFICATE FORMATS.
-S service. Specifies an alternate service (for example, Solaris_8). This service is part of the server and client model, and can only be used from the server's console. Examples. | Exit Status. Attributes. | See Also. Diagnostics. | Warnings. Namepatchadd– apply a patch package to a system running the Solaris operating system. Synopsispatchadd [- dun] [- G] [- Bbackout_dir] [- kkeystore]. Ppasswd] [- t] [- xproxy] {patch} |. Mpatch_location [patch_list]} [- Cnet_install_image |. Rclient_root_path | - Sservice]patchadd- p. Cnet_install_image | - Rclient_root_path | - Sservice]Descriptionpatchadd applies a patch package to a system running the Solaris 2. Solaris environments (such as Solaris 1. Solaris 2. x. This patch installation utility cannot. Solaris 1 patches. The patchadd command has the following forms: The first form of patchadd installs one or more patches to a system, client, service, or to the miniroot of a Net Install Image. The second form of patchadd displays installed patches on the client, service, or to the miniroot of a Net Install Image. Starting with version 1. Solaris operating system, patchadd performs validity and dependency checking among a collection of patches that you specify with the - M source specifier. See the description of - M under OPERANDS, below. With respect to zones(5), when invoked in the global zone, by default, patchadd patches all appropriate packages in all zones. Patching. behavior on system with zones installed varies according to the following factors: use of the - G option (described below)setting of the SUNW_PKG_ALLZONES variable in the pkginfo file (see pkginfo(4))type of zone, global or local (non- global) in patchadd which is invoked. The interaction of the factors above is specified in “Interaction of - G and pkginfo Variable in Zones,” below. When you add patches to packages on a Solaris system with zones installed, you will see numerous zones- related messages, the frequency and content of which depend on whether you invoke patchadd in a global or local zone, the setting of SUNW_PKG_ALLZONES. G option. Note that if you apply a patch that modifies objects in the boot archive, you will need to run the bootadm command shown below. This is true whether the patch is installed individually or as part of a cluster, using install_cluster and specifying an. R /altroot. If you do not enter the preceding command, you will need to boot twice to build a clean boot archive. The patch, - M, - C, - R, and - S arguments shown in the SYNOPSIS are described under OPERANDS, following OPTIONS. Options. The following options are supported: -Bbackout_dir. Saves backout data to a directory other than the package database. Specify backout_dir as an absolute path name.- d. Does not back up the files to be patched. The patch cannot be removed.- GAdd patch(es) to packages in the current zone only. When used in the global zone, the patch is added to packages in the global zone only and is not propagated to packages in any existing or yet- to- be- created non- global zone. When used in a non- global zone, the patch is added to. See “Interaction of - G and pkginfo Variable in Zones,”, below.- kkeystore. Use keystore as the location to get trusted certificate authority certificates when verifying digital signatures found in each patch. If no keystore is specified, then the default keystore locations are searched for valid trusted certificates. See KEY. STORE LOCATIONS in pkgadd(1. M) for more information.- n. Tells patchadd to ignore the signature and not to validate it. This should be used only when the content of the patch is known and trusted, and is primarily included to allow patchadd to apply a patch on systems without the ability to verify. Solaris 8.- p. In the second form, displays a list of the patches currently applied.- Ppasswd.Password to use to decrypt the keystore specified with - k, if required.See PASS PHRASE ARGUMENTS in pkgadd(1.M) for. more information about the format of this option's argument.- t.Maintains the patchadd return codes from the Solaris release prior to Solaris 1. Ms Office 2007 Enterprise Edition By The Shadow Clan Members . On a system with zones(5) installed, a return. Any other return code indicates failure.- u. Turns off validation against other required or incompatible patches. Use extreme caution when using this option. Its use can precipitate unanticipated bad consequences.- xproxy. Specify a HTTP[S] proxy to use when downloading packages The format of proxy is host: port, where host is the hostname of the HTTP[S] proxy, and port is the port number associated. This switch overrides all other methods of specifying a proxy. See ENVIRONMENT VARIABLES in pkgadd(1. M) for more information on alternate methods. Operands. The following operands are supported: Sourcespatchadd must be supplied a source for retrieving the patch. Specify sources using the syntax shown below. The absolute path name to patch_id or a URI pointing to a signed patch. URI pointing to a signed patch.- Mpatch_location [patch_list]Specifies the patches to be installed by directory location or URL and, optionally, the name of a file containing a patch list. When using a directory as the patch_location, specify that directory as an absolute path name. Specify a URL as the server and path name that contains the spooled patches. The optional patch_list is the name of the file at a specified. Mpatch_locationpatch_id [patch_id..]Specifies the patches to be installed by directory location or URL, and patch number. To use the directory location or URL and the patch number, specify patch_location as the absolute path name of the directory that contains spooled patches. Specify a URL as the server and path name that contains the spooled patches. Specify patch_id as. Note that patchadd does not require a list of patches. Among a collection of patches—residing in a directory, specified in a list, or entered on a command line—patchadd performs validity and dependency checking. Specifically, the command. Determines whether a patch is applicable for a system. For example, if the package to be patched is not installed, patchadd does not attempt to add the patch. Establishes dependencies among valid patches and orders the installation of patches accordingly. With the “Zones Parallel Patching” feature, patches can be applied to zones in parallel. After a patch is installed successfully in the global zone, the patch installation software will start a number of processes whose task is to apply patches to zones. The number of processes. The number of processes to be started is determined in the following order: The value of the num_proc parameter. Setting this to 1 retains the current behavior of the patch system. The number of online CPUs in the system. The upper bound is the number of configured Solaris zones. Most users will find the easiest way to specify a source for patchadd is to specify only a patch_location containing a set of patches. Destinations. By default, patchadd applies a patch to the specified destination. If no destination is specified, then the current system (the one with its root filesystem mounted at /) is assumed to be the destination for the patch. You can specify a destination. Cnet_install_image. Patches the files located on the miniroot on a Net Install Image created by setup_install_server. Specify net_install_image as the absolute path name to a Solaris 8 or compatible version boot directory. See EXAMPLES. You should use the - C option only to install patches that are recommended for installation to the miniroot. Patches that are recommended for installation to the miniroot usually include install- related patches such as package commands, and Sun install and patch installation. If you apply too many patches to the miniroot it can grow too large to fit into memory during a net installation of Solaris. Use the - B option and the - C option together so the miniroot does not get too large. See - B, above. Note that in the current release and in certain versions of Solaris 1. To determine whether the miniroot is compressed on your system, look for a file called sparc. Before you can patch a compressed miniroot, you must perform certains steps. See “Patching a Compressed Miniroot” below.- Rclient_root_path. Locates all patch files generated by patchadd under the directory client_root_path. Specify client_root_path as the absolute path name to the beginning of the directory tree under which all patch files generated by patchadd are to be located. R cannot be specified with the - S option. See NOTES. Note – The root file system of any non- global zones must not be referenced with the - R option.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |