HP Tru64 Unix Release Notes for Version 5.1B-6 (5900-1150)

NOTE: With BIND 9, CNAME entries no longer accept quotes. For example, "hosts-1" IN
CNAME A needs to be changed to hosts-1 IN CNAME A.
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 results in an older version of inetd running on your system.
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 takes you to the Technical Updates document:
http://h30097.www3.hp.com/docs/updates/V51B/html/index.html
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 alerts you to potential problems.
Update lprsetup.dat File When Using printconfg
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
AdvFS Domain Differences Can Affect Version Upgrades
A difference in the structure of Version 5.1A and early 5.1B AdvFS domains versus later V5.1B
domains can cause a problem when upgrading to Version 5.1B-4.
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 under 5.1A or an early 5.1B version
and then grows again after a system upgrade to 5.1B-4, the RBMT file can cause any command
that tries to activate that domain to fail. This includes mounting filesets from the affected domain.
Following a system upgrade to Version 5.1B-6 the problem can occur after all the filesets in a
domain are unmounted. (The problem does not occur as long as the filesets remain mounted.)
The solution is to use the fixfdmn utility to correct the problem. For example:
18 Release Notes