HP-UX Containers (SRP) A.03.01 Release Notes

1.8 Limitations for HP-UX Containers A.03.01

When the HP-UX Containers A.03.01 bundle is installed on the system, the following features

will not be available:

1. Installation from a remote network registered SD depot is not supported for software

installation. See the HP-UX Containers (SRP ) A.03.01 Administrator’s Guide for alternative

options.

2. Only the non-interactive command line interface (CLI) for the SD commands is supported

when one or more system containers are configured.

3. Creating a golden image using Ignite-UX with system containers configured is not

supported.

4. DRD clone and modifications with system containers configured is not supported.

1.9 Known issues in HP-UX Containers A.03.01

This section lists known issues and appropriate workarounds:

• The srp_su command does not initialize the TZ environment variable correctly

when the ‘-‘ option is omitted. Executing the srp_su(1M) command without the '-'

option does not update the TZ environment variable for the command or session in the

container based on the container /etc/TIMEZONE variable. The command or session uses

the TZ value set in the global view.

Workaround:

Use the '-' option or set the TZ variable manually when the srp_su command is used

without the '-' option.

• The srp command does not support secondary IP address configuration for

the IPFilter and IPSec services. The srp command supports configuration of multiple IP

addresses for a container. However, the IPFilter and IPSec services for the container will be

configured only for primary IP address and not for secondary IP addresses.

Workaround:

1) Add and apply the IPFilter rules for secondary IP address directly to the

/etc/opt/ipf/ipf.conf file.

2) Use the ipsec_config command to configure HP-UX IPSec to encrypt and

authenticate IP packets between the secondary IP addresses and a remote IP address.

• The srp –import command may reassign file ownership on file restoration

when there are collisions with user or group names in the global view.

When the global view has a user name or group name that matches the ownership of an

import file, the uid and gid assigned to the imported file will be that of the global view

credentials instead of the original uid/gid of the exchange file. This is an underlying

feature of the tar command, which is the tool used for the –export option to create an

exchange file.