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

3. Stop the container:

#srp –stop container_name

• For workload containers: User and group definitions are system properties that are not

container specific and therefore are not exported with the container. The compartment login

permissions for users and groups allowed to login to the container will be exported, but you

must ensure that the required users and groups are configured on the target system, or are

accessible via a common name service, such as LDAP-UX.

For example, to export myContainer and all directories under the myContainer home directory,

enter:

srp –export myContainer export_copy_dirs=/var/hpsrp/myContainer

6.9.2 Using the srp –import command

The srp -import command imports the container contained in the specified exchange file. The

exchange file contains the previously exported container’s configuration, and possibly filesystem

directories. The srp -import command validates the ability of the target system to accept the

exchange file and configures the new container. You can only import a container that does not exist

on the target system.

NOTE: Cloning a container on the same system is not supported.

You can save the exchange file for archival purposes, or you can import it on another system.

The srp -import command has the following syntax:

srp –import [-b[atch]] [-preview] [–xfile <exchange_file>] [variable=<value>...]

Where:

batch

Runs srp -import in batch mode. The command will not prompt for

arguments or template variable values.

preview

Checks whether this system will accept the exchange file for import. If you

specify the preview option, only import validation is performed.

exchange_file

Specifies the existing exchange file name. The srp –export command

creates the exchange file.

The default is srp.exchange.

variable=value

The most commonly used variables for the import operation are as follows:

• iface

The primary network interface name, that is a name without a colon

such as lan0, on which to assign the imported IP address of the

container. Imported IPv4 nework interfaces will be assigned a

secondary interface name, for example lan0:1, if the primary is

already configured in the /etc/rc.config.d/netconf file.

• workload containers: allow_sw_mismatch

Set to yes to force an import operation to succeed if the required

products for the container are not present or if there is a software

version mismatch from the source to the target system. The default is