NAME

patchadd − apply a patch package to a Solaris 2.x system

SYNOPSIS

patchadd [ −d ] [ −u ] [ −B backout_dir ]

[ −C net_install_image | −R client_root_path | −S service ] patch

patchadd [ −d ] [ −u ] [ −B backout_dir ]

[ −C net_install_image | −R client_root_path | −S service ]

−M patch_dir patch_id... | patch_dir patch_list

patchadd [ −C net_install_image | −R client_root_path | −S service ] −p

DESCRIPTION

patchadd applies a patch package to a Solaris 2.x system.  This patch installation utility can not be used to apply Solaris 1.x patches.  patchadd must be run as root. 

There are three forms of the patchadd command. 

The first form of patchadd installs one patch to a system, client, service, or the mini root of a Net Install Image. 

The second form of patchadd installs more than one patch to a system, client, service, or the mini root of a Net Install Image. 

The third form of patchadd displays installed patches on the client, service, or the mini root of a Net Install Image. 

OPTIONS

The following options are supported:

−d Does not back up the files to be patched.  The patch cannot be removed. 

−p Displays a list of the patches currently applied. 

−u Installs unconditionally, turns off file validation.  Applies the patch even if some of the files to be patched have been modified since their original installation. 

−R client_root_path
Locates all patch files generated by patchadd under the directory client_root_path. client_root_path is the directory that contains the bootable root of a client from the server’s perspective.  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. 

−B backout_dir
Saves backout data to a directory other than the package database. Specify backout_dir as an absolute path name. 

−S service Specifies an alternate service (for example,  Solaris_2.3).  This service is part of the server and client model, and can only be used from the server’s console.  Servers can contain shared /usr file systems that are created by Host Manager.  These service areas can then be made available to the clients they serve.  −S cannot be specified with the −R option.  See NOTES. 

−M patch_dir patch_id ... | patch_dir patch_list
Specifies the patches to be installed. Specify patches to the −M option in one of the following ways:

1.  By directory location and patch number. 

To use the directory location and patch number, specify patch_dir as the absolute path name of the directory that contains spooled patches.  Specify patch_id as the patch number of a given patch.  Specifying multiple patch_id’s is recommended.

2.  By directory location and the name of a file containing a patch list. 

To use the directory location and a file containing a patch list, specify patch_dir as the absolute path name of the directory containing the file with a list of patches to be installed.  Specify patch_list as the name of the file containing the patches to be installed. 

−C net_install_image
Patches the files located on the mini root on a Net Install Image created by setup_install_server.  Specify net_install_image as the absolute path name to a Solaris 2.6 or later Net Install Image created by setup_install_server. 

OPERANDS

The following operands are supported:

patch_id The patch number of a given patch.  104945-02 is an example of a patch_id.

patch_list The name of a file that contains a list of patches to install.  patch_list files contain one patch_id on each line. 

patch The absolute path name to patch_id. /var/sadm/spool/patch/104945-02 is an example of a patch.

patch_dir The absolute path name to the directory that contains all the spooled patches.  /var/sadm/spool/patch is an example of a patch_dir. 

EXAMPLES

The examples in this section are all relative to the /usr/sbin directory.  The following example installs a patch to a standalone machine:

example# patchadd /var/spool/patch/104945-02

The following example installs a patch to a client from the server’s console:

example# patchadd −R /export/root/client1 /var/spool/patch/104945-02

The following example installs a patch to a service from the server’s console:

example# patchadd −S Solaris_2.3 /var/spool/patch/104945-02

The following example installs multiple patches in a single patchadd invocation:

example# patchadd −M /var/spool/patch 104945-02 104946-02 102345-02

The following example installs multiple patches specifying a file with the list of patches to install:

example# patchadd −M /var/spool/patch patchlist

The following example installs multiple patches to a client and saves the backout data to a directory other than the default:

example# patchadd −M /var/spool/patch −R /export/root/client1

−B /export/backoutrepository 104945-02 104946-02 102345-02

The following example installs a patch to a Solaris 2.6 or later Net Install Image:

example# patchadd −C /export/Solaris_2.6/Tools/Boot

/var/spool/patch/104945-02

The following example displays the patches installed on a client:

example# patchadd −R /export/root/client1 −p

EXIT STATUS

The following exit values are returned:

0 Successful completion. 

>0 An error occurred. 

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

SEE ALSO

cpio(1), pkginfo(1), patchrm(1M), pkgadd(1M), pkgchk(1M), pkgrm(1M), showrev(1M), attributes(5)

NOTES

To successfully install a patch to a client or server, patchadd must be issued twice, once with the −R option and once with the −S option.  This guarantees that the patch is installed to both the /usr and root partitions.  This is necessary if there are both /usr and root packages in the patch. 

SunOS 5.6  —  Last change: 7 Oct 1996