HP Tru64 UNIX and TruCluster Server Version 5.1.B-4 Patch Summary and Release Notes (13156)

2.2.1.2 Stop sendmail Before Installing Kit (new)
It is important that you stop the sendmail mailer daemon before installing this kit. Failing to
do so can lead to the loss of queued mails. Lost mails cannot be recovered.
To stop the daemon, enter the following command:
# /sbin/init.d/sendmail stop
2.2.1.3 Commands Must Be Run on BIND Systems After Kit Installation (new)
After installing this kit on a system configured to be BIND server, run the following command:
# rcmgr set BIND_SERVERARGS "-c /etc/namedb/named.conf"
On a cluster configured to be a BIND server, run the following command:
# rcmgr -c set BIND_SERVERARGS "-c /etc/namedb/named.conf"
NOTE: Note that in BIND 9, the named daemon uses the c option to pass a configuration file
parameter, instead of the c option that was used in previous versions of BIND.
Stop the named daemon and restart it in order to have the new named daemon take effect:
• For standalone systems:
# /sbin/init.d/named stop
# /sbin/init.d/named start
• For clusters:
# /sbin/init.d/named cluster_stop
# /sbin/init.d/named start
To verify that your configuration files are compatible with Bind 9, run the following commands:
# named-checkconf /etc/namedb/named.conf
# named-checkzone example.com /etc/namedb/hosts.db
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
See “BIND Updated to Version 9.2.5” (page 16) for information about BIND 9.
2.2.1.4 inetd Daemon Restart Required (new)
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.5 Kit Installation Causes Configuration File Restoration Failure (new)
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:
34 Kit Installation and Removal