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

11
Workaround:
Use the '-' option or set the TZ variable manually when the srp_su command is used without
the '-' option.
The srp command allows configuring IPFilter and IPSec Services for only the
primary IP address. The srp command allows configuring more than one 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) Using 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 list command fails to display the custom templates configured on the
container. If a custom template instance is deleted for a container with more than one
custom template instance, then the srp list (-v) command fails to display the custom
instance configured for that container.
Workaround:
To list all the custom template, use the srp list t custom container_name
command.
The srp_init daemon creates a core file if srp_init is restarted within a
container. When the srp_init daemon is terminated and restarted while there are
respawn entries in the container’s /etc/inittab file, the srp_init command will
generate a core file.
Workaround:
Ignore the core file that it creates. The srp_init daemon functionalities are not affected.
The srp_init daemon cannot handle duplicate respawn inittab entries with the
same command name in /etc/inittab. For example:
tst1::respawn:/usr/bin/test
tst2::respawn:/usr/bin/test
The respawn operation for the processes with the same command name does not work
properly. When one of these processes is killed, it will not be respawned immediately, it will
be respawned only after the other process is killed.
Workaround:
Avoid creating duplicate respawn entries with the same command name in the
/etc/inittab.
SRP Manager does not support deleting IPFilter service for application
templates. The SRP Manager does not support deleting IPFilter service from application
templates (such as the apache, sshd, and custom templates).