HP-UX Containers (SRP) A.03.01 Administrator's Guide

84
maintenance (using srp –maint container_A) and then enter the container (using
srp_su –M container_A).
2. Take corrective action based on the information in the swagent.log file.
3. Change the state of the container back to stopped using srp -stop container_A.
4. Install the product by targeting the container:
# swinstall –x local_srp_list="container_A" -s \
/tmp/myproduct_version_2.depot MY_PRODUCT
For swinstall, you can reissue the command without targeting the container since the operation
will proceed to the system container even if the product is installed in the global view. For swremove,
you must target the system container that had the issue, since swremove will not proceed past a
global system in which the remove has already occurred.
In some cases, it can be easier to remove the software from the global view and all system containers
and then install it again in the global view and all system containers.
15.5.6 Advanced installation: varying software versions
For a system container with the private filesystem subtype, the version of software with a kernel
component must match the global view. Versions of other software that contain only user-space
commands, libraries, and GUI can be different from the global view.
During SD operation, you can use the local_srp_list option to skip the global view and target
one or more containers.
The following example shows the swinstall command syntax to install different versions of
MY_PRODUCT in two different containers:
# srp -status
NAME TYPE STATE SUBTYPE ROOTPATH
container_B system started private /var/hpsrp/container_B
container_C system started private /var/hpsrp/container_C
# swinstall -x local_srp_list="container_B" –s \
/tmp/myproduct_version_1.depot MY_PRODUCT
# swinstall -x local_srp_list="container_C" –s \
/tmp/myproduct_version_2.depot MY_PRODUCT
15.5.7 Installation methods other than SD
For products that are managed through installation methods other than HP-UX Software Distributor,
such as the tar command, you can install these products inside each individual system container. If
the product installs files under the /usr or /sbin directories, HP recommends that you use a system
container with a private file system.
15.5.8 Using update-ux with configured containers
The update-ux command lets you update your system to a newer HP-UX 11i v3 Operating
Environment release. When using this command, perform the update-ux policies and procedures
as usual, such as backing up the system and stopping production applications.
After executing the update-ux command, products and patches are installed in the global system
and the system will reboot without prompting. For these reasons, you must stop all containers before
running the update-ux command. The following error is displayed if there are running containers
on the system: