|
Select pages from WAGONEERS.COM: 
Buy this FSJ decal... ...use PayPal to pay for it! 
 |
AMSOIL synthetic lubricants and filters (please use customer #283461) 
Shop AMAZON.com from wagoneers.com!
| |||||||
to write to an NFS mounted filesystem:
swinstall -x write_remote_files=true
swinstall(1M) swinstall(1M)
Hewlett-Packard Company
NAME
swinstall, swcopy - install and configure software products; software
products for subsequent installation or distribution; respectively
SYNOPSIS
swinstall [XToolkit Options] [-i] [-p] [-r] [-v] [-c catalog]
[-C session_file] [-f software_file] [-J jobid] [-Q date] [-s
source] [-S session_file] [-t target_file] [-x option=value] [-X
option_file] [software_selections] [@ target_selections]
swcopy [XToolkit Options] [-i] [-p] [-v] [-C session_file]
[-f software_file] [-J jobid] [-Q date] [-s source] [-S
session_file] [-t target_file] [-x option=value] [-X option_file]
[software_selections] [@ target_selections]
Remarks
+ This command supports operation on remote systems. See the
Remote Operation section below for details.
+ swinstall and swcopy support an interactive user interface that
can be invoked alone or by the sd command. See Interactive
Operation below.
+ For an overview of all SD commands, see the sd(5) man page by
typing man 5 sd on the command line.
DESCRIPTION
The swinstall command installs the software_selections from a software
source to either the local host or to one or more target_selections
(root filesystems). By default, the software is configured for use on
the target after it is installed. (The software is not configured
when installed into an alternate root directory.)
The swcopy command copies or merges software_selections from a
software source to one or more software depot target_selections.
These depots can then be accessed as a software source by the
swinstall command.
Remote Operation
You can enable Software Distributor (SD) to manage software on remote
systems. To let the root user from a central SD controller (also
called the central management server or manager node) perform
operations on a remote target (also called the host or agent):
1) Install a special HP ServiceControl Manager fileset on the remote
systems. This enables remote operations by automatically setting
up the root, host, and template Access Control Lists (ACLs) on the
remote machines and permitting root access from the controller
system. To install the fileset, run the following command on each
remote system:
swinstall -s controller:/var/opt/mx/depot11 AgentConfig.SD-CONFIG
NOTES:
+ controller is the name of the central management server.
+ If the target is running HP-UX 10.20, use the same command but
substitute depot10 for depot11.
+ Targets previously set up by SD/OV to be managed by this
controller do not need this step.
+ SD does not require any other ServiceControl Manager filesets.
2) (Optional) Enable the GUI interfaces for remote operations by
creating the .sdkey file on the controller. Use this command:
touch /var/adm/sw/.sdkey
(This step is not required when you use SD from within the HP
ServiceControl Manager.)
NOTE: You can also set up remote access by using the swacl(1M) command
directly on the remote machines to grant root or non-root access to
users from the controller system.
Interactive Operation
swinstall and swcopy each support a graphical user interface (GUI).
(If your terminal or display cannot support the GUI, these commands
also provide a terminal user interface, in which screen navigation is
done with the keyboard and no mouse.)
To invoke the GUI, enter
swinstall
or
swcopy
on the command line (without any command-line options).
You can also invoke the GUI by including the -i option with any other
command-line options.
The sd command provides an interactive interface for monitoring and
scheduling software jobs. You can also use sd to invoke the swinstall,
copy, and swremove GUIs.
If you have enabled SD's remote operations features, swinstall,
swcopy, and swremove provide enhanced GUIs to support operations on
remote targets. See Remote Operation above for details about enabling
remote operations and the enhanced GUIs.
The command-line version of swinstall can also function interactively
when the ask option is set to true. This option executes an
interactive request script. Request scripts can also be executed by
swconfig and swask. See swconfig(1M)and swask(1M), and the ask=false
default option for more information.
Updating the Operating System
To perform an OS update, HP recommends that you first use the update-
ux command to perform automated update preparation checks and to get
the newest version of swinstall from media. See update-ux(1M) for
more information.
Reinstalling SD
If your copy of SD is unusable, or if you want to install a newer
version of SD, HP recommends that you use the install-sd command.
This command reinstalls SD and also installs any SD patches that exist
in the source depot. See install-sd(1M) for more information.
Installing Kernel Software
In HP-UX, the kernel installation process requires that the system
boots using the kernel at /stand/vmunix. Make sure that your system
is booted to the /stand/vmunix kernel before you install any kernel
software or perform an operating system update.
Dependencies Between Software
The swinstall command supports dependencies, which is software that
must be present or absent before or during the installation of another
piece of software. Dependencies apply between filesets and other
filesets and products. SD supports three types of dependencies:
prerequisites that must be installed and configured before the
dependent fileset is installed and configured (respectively);
corequisites that must be installed and configured before the
dependent is usable. exrequisites that prevent a dependent fileset
from being installed or configured when they are present.
If a software_selection specifies a dependency on other filesets
and/or products, swinstall automatically select that software.
By default, all dependencies must be resolved before swinstall can
proceed. You can override this policy using the enforce_dependencies
option.
Note that if you specify a dependency for a fileset and the fileset is
superseded by another fileset as part of a patch, swinstall still
recognizes the dependency.
Features and Differences between swinstall and swcopy
The key difference between swinstall and swcopy is that swinstall
performs the software installation, while swcopy copies software into
a depot, making it available as a source for installation by
swinstall.
NOTE: To copy to a tape, see the swpackage(1M) manpage.
Other features (differences) include:
+ The swinstall command executes several vendor-supplied scripts
during the installation and configuration of the
software_selections. The swcopy command does not execute
these scripts. The swinstall command supports the following
scripts:
request a script that asks the user questions and
stores responses in a response file. The
response file can then be used by
configuration or other scripts.
checkinstall a script executed during the analysis of a
target_selection, it checks that the
installation can be attempted. If this check
fails, the software product is not installed.
preinstall a script executed immediately before the
software's files are installed.
postinstall a script executed immediately after the
software's files are installed.
configure a script executed during the configuration of
a target_selection, it configures the target
for the software (and the software for the
target). The preinstall and postinstall
scripts are not intended to be used for
configuration tasks. They are to be used for
simple file management needs such as removing
obsolete files from the previous revision
(which was just updated).
unpreinstall a script executed immediately after the
software's actual files are restored if the
software install will fail and the
autorecover_product option is set to true.
The script undoes the steps performed by
preinstall script.
unpostinstall a script executed immediately before the
software's actual files are restored if the
software install failed and the
autorecover_product option is set to true.
The script undoes the steps performed by
postinstall script.
+ When a depot is created or modified using swcopy, catalog
files are built that describe the depot (comparable to the
Installed Products Database (IPD) files that are built by the
swinstall command).
+ By default, the swinstall command only allows the selection of
compatible software from the source. This constraint ensures
that the architecture of the software matches that of the
target_selections. No compatibility checks are performed by
the swcopy command. (A depot can be a repository of software
targeted for a variety of architectures and operating
systems.)
+ By default, swinstall supports updates to higher revisions of
software. If a software_selection of the same revision is
already installed, swinstall will not reinstall it. If a
software_selection has a lower revision than the same software
which is already installed, swinstall will not reinstall it.
(The user can override these behaviors with control options.)
+ The swinstall command creates hard links and symbolic links as
specified for the software. If it encounters a symbolic link
where it expected a regular file, swinstall follows the
symbolic link and updates the file to which it points.
+ The swinstall command does not remove a product's current
files before installing the new ones. A fileset's install
scripts can do that, if necessary. Files being replaced are
overwritten unless they are in use. If in use, they are
unlinked or moved to #. If the autorecover_product
option is set to true; all files are saved to #, and
restored if the install fails.
+ The swinstall command supports kernel building scripts and
rebooting. Before or after software that modifies the kernel
is installed or updated, swinstall executes system-specific
scripts to prepare for or build the new version of the kernel.
The remaining software_selections are then installed. These
scripts are defined in swagent options and include:
install_setup_cmd, system_prep_cmd, kernel_build_cmd, and
install_cleanup_cmd.
After software that requires a system reboot is installed or
updated, swinstall automatically reboots the system. The
reboot command is defined by the swagent option: reboot_cmd.
When updating the operating system (see update-ux(1M) for more
information.), you should install kernel software first to
ensure that a new kernel can be generated before the rest of
the operating system is updated. After all the
software_selections are updated or installed, swinstall
reboots using the new kernel, then executes the configure
scripts for each software_selection. After these scripts
complete, it reboots the system again to restore it to its
normal state.
+ No kernel building or system reboots are performed by swcopy.
+ Both the swinstall and swcopy commands perform various checks
prior to installing or copying the software_selections, for
example disk space analysis.
Options
swinstall and swcopy support the following options:
XToolKit Options
The swinstall and swcopy commands support a subset
of the standard X Toolkit options to control the
appearance of the GUI. The supported options are:
-bg, -background, -fg, -foreground, -display, -
name, -xrm, and -synchronous. See the X(1) manual
page by typing man X for a definition of these
options.
-i Runs the command in interactive mode (Graphical
User Interface). See the Interactive Operation and
Remote Operation headings above for details.
-l (Applies only to HP-UX 10.X.) Runs the command in
linkinstall mode which makes software installed
under a server's shared root available to a
diskless client's private root (HP-UX only).
When run in the linkinstall mode, swinstall:
+ Creates NFS mounts to the software to make it
accessible from the target. This may involve
delayed mounting for alternate roots.
+ Modifies the target's fstab file.
+ Modifies the source's exports file to add mount
permission for the target.
Mounts are created by examining the share_link
product attribute. Not all products support
linkinstall. Some products may be visible without
creating a new mount if they reside under an old one.
-p Previews an install task by running the session
through the analysis phase only.
-r Causes swinstall to operate on alternate root
directories, which must be specified the @
target_selections option. Configuration scripts
are not run on alternate roots. (This option is
not required for alternate root operations but is
maintained for backward compatibility. See the
Alternate Root Directory and Depot Directory
heading in sd(5) for more information.)
-v Turns on verbose output to stdout. (The swinstall
or swcopy logfile is not affected by this option.)
Verbose output is enabled by default; see the
verbose option below.
-c catalog Specifies the pathname of an exported catalog
which stores copies of the response file or files
created by a request script (if -x ask=true or -x
ask=as_needed). The response files are also
stored in the Installed Products Database after
the installation process is complete.
-C session_file
Save the current options and operands to
session_file. You can enter a relative or
absolute path with the file name. The default
directory for session files is
$HOME/.sw/sessions/. You can recall a session
file with the -S option.
-f software_file
Read the list of software_selections from
software_file instead of (or in addition to) the
command line.
-J jobid Executes the previously scheduled job. This is
the syntax used by the daemon to start the job.
-Q date Schedules the job for this date. You can change
the date format by modifying the
/var/adm/sw/getdate.templ file.
-s source Specifies the source depot (or tape) from which
software is installed or copied. (SD can read both
tar and cpio tape depots.) The default source
type is directory. The syntax is:
[host][:][/directory]
A host may be specified by its host name, domain
name, or Internet address. A directory must be
specified by an absolute path.
-S session_file
Execute swinstall or swcopy based on the options
and operands saved from a previous session, as
defined in session_file. You can save session
information from a command-line session with the
-C session_file option.
-t target_file Read the list of target_selections from
target_file instead of (or in addition to) the
command line.
-x option=value
Set the session option to value and override the
default value (or a value in an alternate
option_file specified with the -X option).
Multiple -x options can be specified.
-X option_file Read the session options and behaviors from
option_file.
Operands
The swinstall and swcopy commands support two types of operands:
software selections followed by target selections. These operands are
separated by the "@" (at) character. This syntax implies that the
command operates on "software selections at targets".
Software Selections
The selections operands consist of software_selections.
swinstall and swcopy support the following syntax for each
software_selection:
bundle[.product[.subproduct][.fileset]][,version]
product[.subproduct][.fileset][,version]
+ The = (equals) relational operator lets you specify
selections with the following shell wildcard and pattern-
matching notations:
[ ], *, ?
For example, the following expression installs all bundles
and products with tags that end with "man":
swinstall -s sw_server *man
+ Bundles and subproducts are recursive. Bundles can contain
other bundles and subproducts can contain other subproducts.
For example:
swinstall bun1.bun2.prod.sub1.sub2.fset,r=1.0
or (using expressions):
swinstall bun[12].bun?.prod.sub*,a=HP-UX
+ The \* software specification selects all products. Use this
specification with caution.
The version component has the form:
[,r revision][,a arch][,v vendor]
[,c category][,q=qualifier][,l=location]
[,fr revision][,fa arch]
+ location applies only to installed software and refers to
software installed to a location other than the default
product directory.
+ fr and fa apply only to filesets.
+ The (relational operator) component can be of the form:
=, ==, >=, <=, <, >, or !=
which performs individual comparisons on dot-separated
fields.
For example, r>=B.10.00 chooses all revisions greater than
or equal to B.10.00. The system compares each dot-separated
field to find matches.
+ The = (equals) relational operator lets you specify
selections with the shell wildcard and pattern-matching
notations:
[ ], *, ?, !
For example, the expression r=1[01].* returns any revision
in version 10 or version 11.
+ All version components are repeatable within a single
specification (e.g. r>=A.12, r/swlock (e.g. /var/adm/sw/products/swlock).
swcopy commands that modify a software depot are restricted from
simultaneous modification using fcntl(2) locking on the file
/catalog/swlock (e.g. /var/spool/sw/catalog/swlock).
Read Locks
Both swinstall and swcopy commands set fcntl(2) read locks on source
depots using the swlock file mentioned above. When a read lock is
set, it prevents all SD commands from performing modifications (i.e.
from setting write locks).
Terminal Support
For in-depth information about terminal support refer to:
+ The Software Distributor Administration Guide manual
+ Start the GUI or TUI, select the Help menu, then select the
Keyboard... option to access the Keyboard Reference Guide.
RETURN VALUES
An interactive swinstall or swcopy session always returns 0. A non-
interactive swinstall or swcopy session returns:
0 The software_selections were successfully installed/copied.
1 The install/copy operation failed on all target_selections.
2 The install/copy operation failed on some target_selections.
DIAGNOSTICS
The swinstall and swcopy commands write to stdout, stderr, and to
specific logfiles.
Standard Output
An interactive swinstall or swcopy session does not write to stdout.
A non-interactive swinstall or swcopy session writes messages for
significant events. These include:
+ a begin and end session message,
+ selection, analysis, and execution task messages for each
target_selection.
Standard Error
An interactive swinstall or swcopy session does not write to stderr.
A non-interactive swinstall or swcopy session writes messages for all
WARNING and ERROR conditions to stderr.
Logging
Both interactive and non-interactive swinstall and swcopy sessions log
summary events at the host where the command was invoked. They log
detailed events to the swagent logfile associated with each
target_selection.
Command Log
The swinstall and swcopy commands log all stdout and stderr
messages to the the logfile /var/adm/sw/swinstall.log
(/var/adm/sw/swcopy.log). Similar messages are logged by an
interactive swinstall and swcopy session. The user can specify a
different logfile by modifying the logfile option.
Target Log
A swagent process performs the actual install or copy operation
at each target_selection. For install tasks, the swagent logs
messages to the file var/adm/sw/swagent.log beneath the root
directory (e.g. / or an alternate root directory). For copy
tasks, the swagent logs messages to the file swagent.log beneath
the depot directory (e.g. /var/spool/sw).
You can view the command and target log files with the swjob or sd
command.
Source Depot Audit Log
If both source and target machine are updated to SD revision
B.11.00 or later, the system administrator at the source depot
machine can track which user pulls which software from a depot on
the source machine and when the software is pulled. (Note that a
user running swinstall/swcopy from a target machine cannot set
this option; only the administrator of the source depot machine
can set it. See the source_depot_audit option in the swagent(1M)
man page.)
EXAMPLES
swinstall
To invoke an interactive session of swinstall:
swinstall
Select the C and Pascal products from the network source software
server (sw_server) and start an interactive session:
swinstall -i -s sw_server cc pascal
Install the C and Pascal products to a set of remote hosts:
swinstall -s sw_server cc pascal @ hostA hostB hostC
Update the HP Omniback product from a CD-ROM mounted at /cd :
swinstall -s /cd/swmedia Omniback
Install an incompatible version of HP Omniback into the directory
/exports:
swinstall -x allow_incompatible=true -s/products Omniback,a=arch \
@ /exports
Install all products from the cartridge tape /dev/rmt/0:
swinstall -s /dev/rmt/0 \*
Reinstall the software_selections listed in the file
/tmp/install.products on the hosts listed in the file
tmp/install.hosts:
swinstall -x reinstall=true -f/tmp/install.products \
-t/tmp/install.hosts
Execute swinstall interactively using the session file
/tmp/case.selections as a basis:
swinstall -i -S /tmp/case.selections
Install all the software from local depot /tmp/sample.depot.1, using
any response files generated by request scripts:
swinstall -s /tmp/sample.depot.1 -x ask=true \*
Install Product1 from remote depot /tmp/sample.depot.1 on host swposix
and use an existing response file (previously generated by the swask
command) located in /tmp/bar.depot:
swinstall -s swposix:/tmp/sample.depot.1 -c /tmp/bar.depot
Product1
Install all products in remote depot /tmp/sample.depot.1 on host
swposix, use any response files generated by request scripts, create
catalog /tmp/bar.depot and copy all response files to the new catalog:
swinstall -s swposix:/tmp/sample.depot.1 -c /tmp/bar.depot \
-x ask=true \*
Install all products in remote depot /tmp/sample.depot.1 on host
swposix, use response files, run request scripts only when a response
file is absent, create catalog /tmp/bar.depot and copy all response
files to the new catalog:
swinstall -s swposix:/tmp/sample.depot.1 -c swposix:/tmp/bar.depot \
-x ask=as_needed \*
Install all patches in the depot that correspond to currently
installed software and are of the critical category:
swinstall -s /tmp/sample.depot.1 -x patch_match_target=true \
-x patch_filter=\"*.*, c=critical\"
The following example applies to HP-UX 10.X only.
To linkinstall the product TEST to the clients clientA, clientB from
the server:
swinstall -l -r -s :OS_700 TEST @ clientA clientB
The following example applies to HP-UX 10.X only.
To linkinstall product TEST2 to your own "/" directory from an
application server on "serve":
swinstall -l -s serve TEST2
swcopy
Invoke an interactive session of swcopy:
swcopy
Invoke an interactive session, using default depot at hostX as the
source:
swcopy -i -s hostX
Copy all products from the cartridge tape /dev/rmt/0m to the default
depot on the local host:
swcopy -s /dev/rmt/0m \*
Load the software_selections listed in the file /tmp/load.products
using the default source/depot:
swcopy -f /tmp/load.products
Copy the C and Pascal products to some local and remote depots:
swcopy -s sw_server cc pascal @ /var/spool/sw hostA:/tmp/sw hostB
FILES
$HOME/.swdefaults
Contains the user-specific default values for some or all SD
options. If this file does not exist, SD looks for user-
specific defaults in $HOME/.swdefaults.hosts.
$HOME/.sw/defaults.hosts
Contains the user-specific default list of hosts to manage.
$HOME/.sw/defaults.patchfilters
Contains the user-specific default list of patch filters.
$HOME/.sw/sessions/
Contains session files automatically saved by the SD commands
or explicitly saved by the user.
/usr/lib/sw/sys.defaults
Contains the master list of current SD options with their
default values.
/var/adm/sw/
The directory which contains all of the configurable and non-
configurable data for SD. This directory is also the default
location of logfiles.
/var/adm/sw/defaults
Contains the active system-wide default values for some or all
SD options.
/var/adm/sw/defaults.hosts
Contains the system-wide default list of hosts to manage.
/var/adm/sw/defaults.patchfilters
Contains the system-wide default list of patch filters.
/var/adm/sw/getdate.templ
Contains the set of date/time templates used when scheduling
jobs.
/var/adm/sw/products/
The Installed Products Database (IPD), a catalog of all
products installed on a system.
/var/adm/sw/queue/
The directory which contains the information about all active
and complete install jobs, copy jobs, and other jobs initiated
by the SD commands.
/var/spool/sw/
The default location of a source and target software depot.
AUTHOR
swinstall and swcopy were developed by the Hewlett-Packard Company and
Mark H. Colburn (see pax(1)).
SEE ALSO
swacl(1M), swagentd(1M), swask(1M), swconfig(1M), swjob(1M),
swlist(1M), swmodify(1M), swpackage(1M), swreg(1M), swremove(1M),
swverify(1M), install-sd(1M), update-ux(1M), sd(4), swpackage(4),
sd(5).
Software Distributor Administration Guide, available at
http://docs.hp.com.
SD customer web site at http://software.hp.com/SD_AT_HP/.
Hewlett-Packard Company - 37 - HP-UX Release 11i: November 2000
|
Select pages from WAGONEERS.COM:
Buy this FSJ decal... ...use PayPal to pay for it!
|
AMSOIL synthetic lubricants and filters (please use customer #283461)
Shop AMAZON.com from wagoneers.com!
| |||||||
|
these pages protected by US Copyright laws John Meister copyright © 1995-2001 all rights reserved contact john-at-wagoneers.com | "Join the fight against spam (UCE)! Eliminate spam!" |
Washington State has a $500 fine for "spam" (unsolicited commercial email)! |
read the Bible
