patchsvr(1M)
NAME
patchsvr - set up a local patch server
SYNOPSIS
/usr/sbin/patchsvr setup [-c cache-location] [-d] [-h] [-l]
[-p patch-source-url] [-x web-proxy-host:port]
/usr/sbin/patchsvr start
/usr/sbin/patchsvr stop
/usr/sbin/patchsvr enable
/usr/sbin/patchsvr disable
DESCRIPTION
The patchsvr command enables you to set up a local patch
server on your intranet. The setup subcommand configures the
local patch server. The start and stop subcommands start and
stop the local patch server. Finally, the enable and disable
subcommands permit you to start up and prevent startup of
the local patch server at boot time.
Configuring Your Local Patch Server
By default, Sun Patch Manager expects that your local sys-
tems are connected, via the Internet, to the Sun patch
server to be analyzed and to receive patches. By using a
local patch server instead, you can minimize the Internet
traffic and serve your local systems from a patch server on
your intranet.
The system you choose to act as the local patch server must
be running at least Solaris 9 and have the Developer
Software Support Group installed. If your system runs
Solaris 9, it must also have the Sun Patch Manager 2.0
software installed. If your system runs Solaris 10 and has
the Developer Software Support Group installed, the Sun
Patch Manager 2.0 software is included.
The use of a local patch server addresses security concerns
and reduces the amount Internet traffic between the Sun
patch server and your client systems.
For instance, instead of having to download patches and
metadata from the Sun patch server to each of your systems,
you only need to perform this download once to the local
patch server. After the patch data is stored on your local
patch server, the transfer of patch data to your system for
analysis is done over your intranet instead of over the
Internet.
You can configure a chain of patch servers on your intranet.
The last link in the chain of local servers can point to the
Sun patch server or to a local collection of patches. By
using this chain of servers, a patch download request from
your system to its primary patch server can be forwarded to
other servers in the chain in an attempt to fulfill the
request. So, if your system's primary server cannot locate a
patch, the server makes the same request of the next server
in the chain to see if the patch is stored there. If the
patch is found, it is downloaded to the system. If the patch
is not found, the request continues along the chain until
the patch is found or the terminal point in the chain is
reached.
Each server in the chain stores the patches found on another
server in the chain based on the download request. So, a
patch that is not initially found on your local server will
be downloaded to your local server and stored before being
downloaded to the client system.
Your local patch server must specify the source of patches
to use. By default, the server obtains patches from the Sun
patch server, but it can also obtain patches from another
patch server in the chain or from a collection of patches on
your system.
You must specify the URL that points to the collection of
patches. By default, the Sun patch server is the source of
patches. The URL is:
https://updateserver.sun.com/solaris/
Note that this URL must appear as a single line.
This URL must point to another server in the chain or to a
collection of patches on the local system. This URL cannot
be null.
Starting and Stopping Your Local Patch Server
The patchsvr start command starts the local patch server on
a system that runs the Sun Patch Manager 2.0 software. You
can also enable the boot-time startup of the local patch
server by running patchsvr enable.
The patchsvr stop command stops the local patch server on a
system that runs the Sun Patch Manager 2.0 software. You can
also disable the boot-time startup of the local patch server
by running patchsvr disable.
Before you use your local patch server for the first time,
you must run the patchsvr start command.
Use these commands when you want to change the configuration
of your local patch server. Before you use the patchsvr
setup command to change the configuration parameter values,
you must stop your local patch server. Then, you can update
the configuration values. Finally, you must restart the
local patch server.
OPTIONS
The following options are supported for the patchsvr setup
command:
-c cache-location
Specifies the location of the server's cache, also
known as the patch repository. This is the directory
in which downloaded patches are stored on the local
patch server. You must specify a full path to the
cache location. By default, the cache location is
file:/var/sadm/spool/patchsvr.
-d Resets the local patch server configuration settings
to the default values.
-h Displays information about the command-line options.
-l Lists the configuration settings for the patch server.
-p patch-source-url
Specifies the URL that points to the collection of
patches. By default, the URL points to the Sun patch
server:
https://updateserver.sun.com/solaris/
Note that this URL must appear as a single line.
-x web-proxy-host:port
Specifies the local web proxy. If the local patch
server is behind a firewall, use this option to
specify the web proxy that accesses the Internet. Get
the name of the web proxy, web-proxy-host, and its
port, port, from your system administrator or network
administrator. The default port value is 3816.
Do not use this option if you are accessing patch data
from a collection of patches on the local patch
server.
EXAMPLES
Example 1: Changing the Cache Location
# patchsvr setup -c /var/patch/cache
Example 2: Specifying the Sun Patch Server as the Source of
Patches
# patchsvr setup -p https://updateserver.sun.com/solaris/
The Sun patch server is the default source of patches.
Example 3: Specifying a Local Patch Server as the Source of
Patches
# patchsvr setup -p http://patchsvr1:3816/solaris/
Specifies the system called patchsvr1, a local patch server,
as the source of patches.
Example 4: Specifying a CD as the Source of Patches
# patchsvr setup -p file:/cdrom/cdrom0
Specifies the CD mounted from the first CD-ROM drive of the
local system as the patch source.
Example 5: Specifying a Web Proxy
# patchsvr setup -x webproxy:3816
Specifies the host name, webproxy, and port, 3816, of the
web proxy that your local patch server uses to connect to
the Internet.
Example 6: Resetting the Configuration Settings to the
Default Values
# patchsvr setup -d
Example 7: Listing the Configuration Settings for Your Local
Patch Server
# patchsvr setup -l
Patch source URL: https://updateserver.sun.com/solaris/
Cache location: /var/sadm/spool/patchsvr
Web proxy host name: mars
Web proxy port number: 3816
Shows the configuration settings, which include information
about the source of patches, the location of the cache
directory, and, if needed, a web proxy and port.
Example 8: Starting the Local Patch Server
# patchsvr start
Example 9: Stopping the Local Patch Server
# patchsvr stop
Stops your local patch server. While the patch server is
stopped, you can change the configuration settings for your
local patch server, then restart it.
Example 10: Enabling the Boot-Time Startup of the Local
Patch Server
# patchsvr enable
Example 11: Disabling the Boot-Time Startup of the Local
Patch Server
# patchsvr disable
ATTRIBUTES
See the attributes(5) man page for descriptions of the fol-
lowing attributes:
____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Availability | SUNWpsvru |
|_____________________________|_____________________________|
| Interface Stability | Evolving |
|_____________________________|_____________________________|
SEE ALSO
smpatch(1M), attributes(5)
Solaris Administration Guide: Basic Administration
Man(1) output converted with
man2html