| United States-English |
|
|
|
![]() |
HP Tru64 UNIX: Release Notes for Version 5.1B-4 > Chapter 3 Release Notes3-4 General Release Notes |
|
The release notes in this section describe issues you might encounter and, when available, provide workarounds you can use. As a consequence of the rebranding of Tru64 UNIX from the Compaq name to HP, the following files have changed:
The .mrg..sysconfigtab file has been modified to incorporate these changes into the generic sysconfig subsystem in the /etc/sysconfigtab file. If the rebranding of HP Tru64 UNIX version information impacts any applications or layered products, you can manually change generic system version attributes. See the sysconfigtab(4) and sys_attrs_generic(5) reference pages for more information on how to modify generic system version attributes. The following error messages are displayed when you install the IOSJPAPXBASE540 and IOSJPAPXGUI540 subsets onto the system-installed APXBASE122 and APXGUI122 subsets:
These errors are caused by a dependency of the Japanese Advanced Printing Software subsets on the corresponding original Advanced Printing Software subsets APXBASE120 and APXGUI120, despite the changed subset names of APXBASE122 and APXGUI122 in APCD1 for the V5.1B-4 release. You can avoid these errors by creating APXBASE120.lk and APXGUI120.lk files in the /usr/.smdb. directory temporarily after installing APXBASE122 and APXGUI122 as following:
The performance of secure FTP (sftp) will be always less than ftp due to the authentication and encryption involved in sftp communication. The transfer rate of sftp depends on the type of authentication it employs. You can achieve better transfer rate performance by choosing the Message Authentication Code (MAC) algorithm hmac-md5 for authentication, but at the cost of security. The default MAC is hmac-sha1, which is more secure than hmac-md5. See sftp(1) for information about secure FTP and ssh2_config(4) for information about supported MACs and ciphers. Some Insight Manger components included in Tru64 UNIX Version 5.1B-4, such as cpq_mibs and the config_hmmod and sysman_hmmod daemons, might core dump during reboots. You can correct this problem by installing the latest version of the Insight Manager, Version 3.6. You can download this version from the HP Insight Management Agents for Tru64 UNIX Web site: http://h30097.www3.hp.com/cma/ If you have not installed Version 3.6 and the Insight Manager processes do not run after you reboot your system, restart them using the Insight Manger startup scripts. A firmware upgrade to v1.50 or N14r on the 1x8 Autoloader causes the WWID to change. As a result, the existing device associated with the media changer is no longer accessible. For complete details see the Customer Advisory available at: If when booting your system you see a message similar to the following, rebooting your system may be able to re-enable the hardware:
If the reboot fails, call your HP service representative to have the unit repaired. Do not use dxarchiver command to verify a bootable tape. Instead, use the mt and restore commands as follows:
The first command skips the first file on the tape. When preparing for a btcreate session, verify the size of the file system to ensure that you have sufficient tape volumes, depending on the maximum storage capacity of your tape device. The btcreate command prompts you to load a new tape volume if it runs out of storage space. Label the tapes in sequence. If the /var/yp/securenets file is in use as part of NIS, it must contain the following localhost entry:
If the /var/yp/securenets file is used without a localhost entry, you will see severe delays on logins. See ypserv(8) for more information. The Security Integration Architecture (SIA) sialog logging process is intended only for use in debugging SIA problems. It should not be enabled for extended periods of time. Doing so can cause login delays or other problems. Use the audit , not the sialog process , subsystem to monitor authentications on the system. To disable sialog debug logging, delete the /var/adm/sialog file. For more information, see the sialog(4) and sia_log(3) reference pages and the Tru64 UNIX Security Programming document. |
||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||