HP Tru64 UNIX and TruCluster Server Version 5.1B-5 Patch Summary and Release Notes (March 2009)

2.2.1.5 inetd Daemon Restart Required
Because of changes made to the Internet services daemon introduced in this release,
you need to stop and then restart inetd after installing or removing this kit. You can
do this from the command line or by using the sysman application. From the command
line, enter the following commands:
# /sbin/init.d/inetd stop
# /sbin/init.d/inetd start
Failure to do this will result in an older version of inetd running on your system.
2.2.1.6 Kit Installation Causes Configuration File Restoration Failure
After installing this kit, attempts to restore the configuration file (config.cdf) saved
prior to the installation of this patch will fail due to a checksum error. You can, however,
force the operation by using the following sysman command:
# sysman -clone -apply -force config.cdf
For more information, see the note titled Correction to Configuration Cloning Restrictions
in the “Corrections to Manuals” section of the online Technical Updates document for
Version 5.1B. The following link will take you to the Technical Updates document:
http://h30097.www3.hp.com/docs/updates/V51B/html/index.html
2.2.1.7 Run ipsec Command After Installing Kit
If you are running IP Security (ipsec) on your system, run the following command
after installing this kit to determine if any unsafe connections exist:
# /usr/sbin/sysman ipsec
A warning message will alert you to any potential problems.
2.2.1.8 Procedure to Update lprsetup.dat File
If you use the /usr/sbin/printconfig application to configure printer queues,
run the following command as root to update the /etc/lprsetup.dat file:
# /usr/sbin/lprsetup -c update
2.2.1.9 AdvFS Domain Differences May Affect Version Upgrades
A difference in the structure of Version 5.1A and early 5.1B AdvFS domains verses
later V5.1B domains can cause a problem when upgrading to Version 5.1B-4 or higher.
This potential problem involves a metadata file called the RBMT that exists on each
volume of a version 4 domain.
Although an RBMT is generally only one page long, it can be longer on large volumes
or domains that have many files. If an RBMT file was larger than one page long under
5.1A or an early 5.1B version and then grows again after a system upgrade to Version
5.1B-4 or higher, the RBMT file can cause a problem in which any command that tries
26 Kit Installation and Removal