swinstall.1m (2011 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

swinstall(1M) swinstall(1M)

NAME

swinstall, swcopy - install and conﬁgure software products; software products for subsequent installation

or distribution; respectively

SYNOPSIS

swinstall [XToolkit Options ][

-i][-p][-r][-v][-c

catalog ][-C session_ﬁle ]

[

-f software_ﬁle][

-J jobid ][-Q date ][-s source ][-S session_ﬁle ][

-t target_ﬁle ]

[

-x option=value ][-X option_ﬁle ][software_selections][

@ target_selections]

swcopy [XToolkit Options ][

-i][-p][-v][-C session_ﬁle ][

-f software_ﬁle ][-J jobid ]

[

-Q date ][-s source ][

-S session_ﬁle ][-t target_ﬁle ][-x option=value ][

-X option_ﬁle ]

[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

man5sdon the com-

mand 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 ﬁlesystems). By default, the software is conﬁgured for use on the

target after it is installed. (The software is not conﬁgured when installed into an alternate root direc-

tory.)

When

HP-UX Secure Resource Partitions (SRPv3) is installed and enabled, the

swinstall

command behavior is changed to support software management for SRP system containers (refer to

srp(5)).

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

swin-

stall 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 opera-

tions on a remote target (also called the host or agent):

1) Set up the root, host, and template Access Control Lists (ACLs) on the remote machines to permit

root access from the controller system. To do this, run the following command on each remote sys-

tem:

/usr/lib/sw/mx/setaccess controller

NOTES:

• controller is the name of the central management server.

• If remote system is 11.00, make sure SD patch PHCO_22526 or a superseding patch is installed

on remote system before running

setaccess.

• If remote system is older than 11.00 or for some other reason does not have

setaccess in place,

copy setaccess script from an 11.11 or higher system to the remote system.

swinstall, swcopy, and swremove have enhanced GUI interfaces for remote operations. Enable

the enhanced GUIs by creating the .sdkey ﬁle on the controller. Use this command:

touch /var/adm/sw/.sdkey

NOTE: You can also set up remote access by using swacl 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 naviga-

tion is done with the keyboard and no mouse.)

HP-UX 11i Version 3: September 2011 − 1 − Hewlett-Packard Company 1

Summary of content (24 pages)

PAGE 1
swinstall(1M) swinstall(1M) 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
PAGE 2
swinstall(1M) swinstall(1M) 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.
PAGE 3
swinstall(1M) swinstall(1M) 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.
PAGE 4
swinstall(1M) swinstall(1M) 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.
PAGE 5
swinstall(1M) swinstall(1M) -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 .
PAGE 6
swinstall(1M) swinstall(1M) • Fully qualified software specs include the r=, a=, and v= version components even if they contain empty strings. For installed software, l= is also included. • No space or tab characters are allowed in a software selection. • The software instance_id can take the place of the version component. It has the form: [instance_id ] within the context of an exported catalog, where instance_id is an integer that distinguishes versions of products and bundles with the same tag.
PAGE 7
swinstall(1M) swinstall(1M) • If you set the value of this option to HOME/path , SD replaces HOME with the invoking user’s home directory (from the system password file) and resolves path relative to that directory. For example, HOME/my_admin resolves to the my_admin directory in your home directory. • If you set the value of the installed_software_catalog default option to a relative path, that path is resolved relative to the value of this option.
PAGE 8
swinstall(1M) swinstall(1M) If set to ask=true, or ask=as_needed, you can use the -c catalog option to specify the pathname of an exported catalog to store copies of the response file or files created by the request script. See swask (1M) for more information on request scripts. autoreboot=false (Applies only to swinstall.) Prevents the installation of software requiring a reboot from the non-interactive interface.
PAGE 9
swinstall(1M) swinstall(1M) the requisite is explicitly selected by the user. When set to true, the first left-most dependency in a list of OR dependencies that satisfies a requisite is not automatically selected when another dependency in the list that also satisfies the requisite is explicitly selected.
PAGE 10
swinstall(1M) swinstall(1M) • INDEX.gz or INFO.gz are not older than the corresponding uncompressed INDEX or INFO files. The uncompressed INDEX or INFO file is accessed by the source agent if any problem occurs when accessing, transferring, or uncompressing the INDEX.gz or INFO.gz file. controller_source= Specifies the location of a depot for the controller to access to resolve selections. Setting this option can reduce network traffic between the controller and the target.
PAGE 11
swinstall(1M) swinstall(1M) If set to false, dependencies are still checked, but not enforced. Corequisite dependencies, if not enforced, may keep the selected software from working properly. Prerequisite dependencies, if not enforced, may cause the installation or configuration to fail. enforce_dsa=true Prevents the command from proceeding past the analysis phase if the disk space required is beyond the available free space of the impacted filesystem(s).
PAGE 12
swinstall(1M) swinstall(1M) Caution: use a specific installed_software_catalog to manage a specific application. SD does not support multiple descriptions of the same application in multiple IPDs. See also the admin_directory and run_as_superuser options, which control SD’s nonprivileged mode. (This mode is intended only for managing applications that are specially designed and packaged. This mode cannot be used to manage the HP-UX operating system or patches to it.
PAGE 13
swinstall(1M) swinstall(1M) 0 1 2 provides no information to the logfile. enables verbose logging to the logfiles. enables very verbose logging, including per-file messages, to the logfiles. log_msgid=0 Adds numeric identification numbers at the beginning of SD logfile messages: 0 (default) No identifiers are attached to messages. 1 Adds identifiers to ERROR messages only. 2 Adds identifiers to ERROR and WARNING messages. 3 Adds identifiers to ERROR, WARNING, and NOTE messages.
PAGE 14
swinstall(1M) swinstall(1M) is_patch=true attribute) that correspond to software on the target root or depot. If multiple targets are specified, the first target in the list is used as the basis for patch selections. The patch_filter= option can be used in conjunction with patch_match_target. patch_save_files=true (Applies only to swinstall) Saves the original versions of files modified by patches, which permits the future rollback of a patch. Patched files are saved to /var/adm/sw/save.
PAGE 15
swinstall(1M) swinstall(1M) remove_obsolete_filesets=false (Applies only to swcopy.) Controls whether swcopy automatically removes obsolete filesets from target products in the target depot. If set to true, swcopy removes obsolete filesets from the target products that were written to during the copy process. Removal occurs after the copy is complete. Filesets are defined as obsolete if they were not part of the most recent packaging of the product residing on the source depot.
PAGE 16
swinstall(1M) swinstall(1M) rpc_binding_info_target= Defines the protocol sequence(s) and endpoint(s) on which commands contact the daemon for target access only. If the connection fails for one protocol sequence, the next is attempted. If this is set to no value (default) the values from rpc_binding_info are used to contact the daemon for target access. See rpc_binding_info (above) for more information. rpc_timeout=5 Relative length of the communications timeout.
PAGE 17
swinstall(1M) swinstall(1M) source_tape=/dev/rmt/0m Defines the default location of the source tape, usually the character-special file of a local tape device. You can also use the [host ]:[path ] syntax, but the host must match the local host. The -s option overrides this value. (Note that SD can read both tar and cpio tape depots.) source_type=directory Defines the default source type: cdrom, directory, or tape. The source type derived from the -s option overrides this value.
PAGE 18
swinstall(1M) swinstall(1M) Additionally, the swinstall and swcopy interactive user interfaces read a default list of hosts on which to operate. The list is stored in: /var/adm/sw/defaults.hosts the system-wide default list of hosts $HOME/.swdefaults.hosts the user-specific default list of hosts For each interactive command, target hosts containing roots and target hosts containing depots are specified in separate lists ( hosts, hosts_with_depots, respectively).
PAGE 19
swinstall(1M) swinstall(1M) example, subscripts). SW_CONTROL_TAG Holds the tag name of the control_file being executed. When packaging software, you can define a physical name and path for a control file in a depot. This lets you define the control_file with a name other than its tag and lets you use multiple control file definitions to point to the same file. A control_file can query the SW_LOCATION Defines the location of the product, which may have been changed from the default product directory.
PAGE 20
swinstall(1M) swinstall(1M) HP-UX kernel filesets are also reboot filesets, the values of this variables is always equal to the value of SW_SESSION_IS_KERNEL. SW_SESSION_IS_UPDATE A value of 1 indicates the SD command was invoked by the update-ux command during an Operating System update. This variable is set by the update-ux command. SW_SYSTEM_FILE_PATH The path to the kernel’s system file. The default value is /stand/system.
PAGE 21
swinstall(1M) swinstall(1M) 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.
PAGE 22
swinstall(1M) swinstall(1M) 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.
PAGE 23
swinstall(1M) swinstall(1M) $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.
PAGE 24
(Notes) A (Notes) sA 24 Hewlett-Packard Company −1− HP-UX 11i Version 3: September 2011