Patch Manager is configured to use these default locations for storing patch-related data:
Download directory – Directory in which patches are stored when they are downloaded from the patch source. This is also the directory from which patches are applied. Patches remain in this directory until they are successfully applied. The default location is /var/sadm/spool.
Backout data directory – Directory in which data that enables a patch to be backed out is stored. By default, backout data is stored in the default locations used by patchadd. This is the save directory of each package that was modified by the patch. For example, if a patch modifies the SUNWcsr package, the backout data for that package is stored in the /var/sadm/pkg/SUNWcsr/save directory.
If you run out of available disk space in the default locations, specify different locations for these directories.
If you specify a different directory, you must manually create that directory before performing any patch operations.
Determine the new locations for the directories.
Become an appropriately authorized user or assume a role that includes the Software Installation profile or the solaris.admin.patchmgr.* authorization.
The System Administrator profile includes the appropriate profiles. To create the role and assign the role to a user, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
Specify a new directory, dir-name, for any of the patch-related directories.
To specify a different download directory, type:
# smpatch set patchpro.download.directory=dir-name |
For example, dir-name is /export/patches.
To specify a different backout directory, type:
# smpatch set patchpro.backout.directory=dir-name |
For example, dir-name is /export/patches/backout.