Use the smpatch command to perform the configuration tasks in this section. For the list of configuration parameters you can set, see Setting Patch Manager Configuration Parameters and the smpatch(1M) man page.
If you want to use the browser interface to configure your patch management environment, see Configuring Your Patch Management Environment by Using the Browser Interface (Task Map).
By default, the patch management environment is configured to obtain patches directly from the Sun patch server. Therefore, you must customize your environment if your system does one or more of the following:
Connects to the Internet by means of a web proxy
Requires a user name and password to obtain patches
Obtains patches from a patch source other than the Sun patch server
The following table identifies the tasks that you might perform when you configure the patch management environment for your system.
Task |
Description |
For Instructions |
---|---|---|
(Optional) Specify the web proxy to use. |
If your system is connected to the Internet through a web proxy, you must specify the web proxy that is used to access the Sun patch server. By default, no web proxy is specified. | |
(Optional) Specify the user and password needed to provide authentication for the web proxy. |
If your web proxy requires authentication, you must specify the web proxy user that is needed for authentication. By default, no web proxy user is specified. | |
(Optional) Specify the user and password needed to obtain patches from the Sun patch server. |
If you needed a user and password to obtain patches, you must specify the user name and password. |
How to Specify a User Name and Password With Which to Obtain Patches (Command Line) |
(Optional) Specify the source of patches for your system. |
Your system can obtain patches from one of the following sources:
The default source of patches for your system is the Sun patch server. |
The following procedures and examples show how to run the local mode smpatch command, which is run by default. To run the remote mode version, use any of the authentication options (except for -L) or the remote options. See the smpatch(1M) man page.
If your system connects to the Internet through a web proxy, you must provide information about the web proxy to Patch Manager.
Obtain the host name and the port of the web proxy from your network administrator.
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 the web proxy.
# smpatch set patchpro.proxy.host=web-proxy-server \ patchpro.proxy.port=port |
(Optional) If the web proxy requires authentication, supply the user name and password.
Obtain this information from your network administrator.
Specify the user name to be used for authentication.
# smpatch set patchpro.proxy.user=web-proxy-user |
Specify the proxy user's password by having smpatch prompt you for the password.
# smpatch set patchpro.proxy.passwd Web Proxy User Password: web-proxy-password |
Setting the password in this way ensures that the password you type does not appear as clear text in the following:
Standard output
Output of the ps command
Your shell history file
If you needed a user name and password to obtain patches from the Sun patch server, you must specify them for Patch Manager.
If you do not have an account on SunSolve, register for one at http://sunsolve.sun.com.
As of June 2005, a user name and password are not required to obtain patches from the Sun patch server.
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 your user name.
# smpatch set patchpro.sun.user=user-name |
Specify the password for your user by having smpatch prompt you for the password.
# smpatch set patchpro.sun.passwd Sun User Password: password |
Setting the password in this way ensures that the password you type does not appear as clear text in the following:
Standard output
Output of the ps command
Your shell history file
Your system can obtain patches from the following sources:
Sun patch server
Local patch server on your intranet
Local patch collection
By default, your system obtains patches from the Sun patch server.
The local patch server is an optional Sun Patch Manager 2.0 feature that you can obtain at no charge if you are a contract customer in the SunSpectrum program.
For information about becoming a contract customer or obtaining the local patch server distribution, go to http://sunsolve.sun.com and click Patch Portal.
If you want your system to obtain patches from a local patch server, you must first configure one. See Configuring Your Local Patch Server (Task Map).
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 the URL of the patch source.
For the Sun patch server, type:
# smpatch unset patchpro.patch.source |
For a local patch server, use this URL format:
# smpatch set patchpro.patch.source=http://server-name:3816/solaris/ |
For a collection of patches in a directory, use this URL format:
# smpatch set patchpro.patch.source=file:/directory-name |
Note that directory-name can be a local file system or a remotely mounted file system.
See Example 5–2 for examples of using the file:/ URL format.
The following example shows how to configure a system to obtain patches from the /export/patches directory on the local system.
# smpatch set patchpro.patch.source=file:/export/patches |
The following example shows how to configure a system to obtain patches from the /export/patches directory on the remote system called jupiter.
# smpatch set patchpro.patch.source=file:/net/jupiter/export/patches |
The following example shows how to configure a system to obtain patches from a CD mounted from the first CD-ROM drive of the local system.
# smpatch set patchpro.patch.source=file:/cdrom/cdrom0 |
After you specify a patch source, your client system is ready to manage patches. See Managing Patches by Using the Command-Line Interface (Task Map).