ULTRIX and UWS Version 4.5 Release Notes Order Number: AA-PZTXC-TE September 1995 Product Version: ULTRIX and UWS Version 4.5 This manual lists new features and changes to the ULTRIX and UWS products. It also discusses current product software and documentation issues. FIELD TEST 2 DRAFT This is an unpublished work containing confidential and secret information which is protected under the copyright laws. The existence of a copyright notice is not to be construed as an admission or presumption that publication has occurred. Unauthorized copying is strictly prohibited. __________________________________________________ Digital Equipment Corporation Maynard, Massachusetts Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Portions of the information herein are derived from copyrighted material as permitted under license agreements with AT&T and the Regents of the University of California. Copyright AT&T 1979, 1984. All Rights Reserved. Portions of the information herein are derived from copyrighted material as permitted under a license agreement with Sun Microsystems, Inc. Copyright Sun Microsystems, Inc, 1985. All Rights Reserved. Portions of this document Copyright Massachusetts Institute of Technology, Cambridge, Massachusetts, 1984, 1985, 1986, 1988. Portions of this document Copyright Digital Equipment Corporation 1992, 1993, 1994, 1995. All rights reserved. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, Alpha AXP, AlphaGeneration, AlphaServer, AlphaStation, AXP, Bookreader, CDA, DDIS, DEC, DEC Ada, DEC Fortran, DEC FUSE, DECnet, DECstation, DECsystem, DECterm, DECUS, DECwindows, DTIF, MASSBUS, MicroVAX, OpenVMS, POLYCENTER, Q-bus, TURBOchannel, ULTRIX, ULTRIX Mail Connection, ULTRIX Worksystem Software, UNIBUS, VAX, VAXstation, VMS, XUI, and the DIGITAL logo. AIX is a registered trademark of International Business Machines Corporation. Domain and AEGIS are registered trademarks of Apollo Computer, Inc., a subsidiary of Hewlett-Packard Company. IBM is a registered trademark of International Business Machines Corporation. INGRES is a registered trademark of Ingres Corporation. Intel is a trademark of Intel Corporation. Interleaf is a registered trademark of Interleaf, Inc. Prestoserve is a trademark of Legato Systems, Inc.; the trademark and software are licensed to Digital Equipment Corporation by Legato Systems, Inc. Legato NetWorker is a trademark of Legato Systems, Inc. Lotus is a registered trademark of Lotus Development Corporation. MIPS is a trademark of MIPS Computer Systems, Inc. NFS is a registered trademark of Sun Microsystems, Inc. Open Software Foundation, OSF, OSF/1, OSF/Motif, and Motif are trademarks of the Open Software Foundation, Inc. Adobe, PostScript, and Display PostScript are registered trademarks of Adobe Systems, Inc. Sun is a registered trademark of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. X/Open is a trademark of X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. Contents About This Manual Audience ............................................ vii Organization ........................................ vii Related Documentation ............................... viii Conventions ......................................... ix 1 Installation and Upgrade 1.1 New Features and Changes ...................... 1-1 1.2 Installation and Upgrade Notes ................ 1-1 1.2.1 Larger Swap Space Needed ................. 1-1 1.2.2 Delete XUI Subsets Before Upgrading to OSF/Motif .................................. 1-2 1.2.2.1 Do Not Apply Previously Published Patches to Version 4.5 ................. 1-2 1.2.2.2 Field Test Systems Must Remove Certain Lock Files Before Upgrade ...... 1-2 1.2.2.2.1 Removing Lock files from RISC Systems ............................. 1-2 1.2.2.2.2 Removing Lock Files from VAX Systems ............................. 1-3 1.2.2.3 Stopping Installation with Ctrl/C .. 1-4 1.2.2.4 Loading Software Updates During an Upgrade ................................ 1-4 1.2.2.5 Rebuilding the Kernel During an Upgrade ................................ 1-4 1.2.3 Software Media and Subsets ............... 1-4 1.2.3.1 VAX Console Media Labeling Differences ............................ 1-4 1.2.3.2 Media Labels ....................... 1-5 1.2.3.3 ULTRIX and UWS RISC Subset Sizes ... 1-8 1.2.3.3.1 Sizes of ULTRIX and UWS RISC Supported Subsets ................... 1-8 1.2.3.3.2 Sizes of ULTRIX and UWS RISC Unsupported Subsets ................. 1-10 1.2.3.3.3 Sizes of ULTRIX and UWS RISC Boot Upgrade Subsets ................ 1-11 1.2.3.3.4 Sizes of ULTRIX and UWS RISC Encryption Kit Subsets .............. 1-12 1.2.3.4 Sizes of ULTRIX and UWS VAX Subsets 1-13 1.2.3.4.1 Sizes of ULTRIX and UWS VAX Supported Subsets ................... 1-13 1.2.3.4.2 Sizes of ULTRIX and UWS VAX Unsupported Subsets ................. 1-15 1.2.3.4.3 Sizes of VAX Boot Upgrade Subsets ............................. 1-16 1.2.3.4.4 Sizes of VAX Encryption Kit Subsets ............................. 1-17 1.2.4 Booting the System ....................... 1-17 1.2.5 RIS and DMS Notes ........................ 1-18 1.2.5.1 ULTRIX RIS Servers and Digital UNIX Clients ................................ 1-18 1.2.5.2 Space Needed to Install ULTRIX and UWS in RIS and DMS Areas ............... 1-18 1.2.5.3 DMS Modify Option Could Fail with Client on Different Subnet ............. 1-18 1.2.6 After the Upgrade or Installation ........ 1-19 1.2.6.1 Change the disktab File after All Upgrades ............................... 1-19 1.2.6.2 Ensuring that lockd and statd are Running ................................ 1-20 1.2.6.3 Removing "proto" Files After Install or Upgrade ............................. 1-20 1.2.6.4 Deleting genvmunix After an Installation ........................... 1-20 1.2.6.5 Delete Lock Files When Reconfiguring from Motif to XUI ...................... 1-20 1.2.7 Subset Changes ........................... 1-21 1.2.7.1 System Management Subset Changes ... 1-21 1.2.7.2 Prototype Subset for RISC Systems .. 1-21 iv Contents 2 Hardware 3 ULTRIX Software 3.1 New Features and Changes ...................... 3-1 3.1.1 New Option to param.c File ............... 3-1 3.1.2 New ypserv(8yp) Command Option ........... 3-2 3.1.2.1 New YP Control File ................ 3-2 3.2 ULTRIX Notes .................................. 3-3 3.2.1 Printing Notes ........................... 3-3 3.2.1.1 The lprsetup Command ............... 3-3 3.2.1.2 The DECprinter Print Filter ........ 3-3 4 ULTRIX Worksystem Software 4.1 New Features and Changes ...................... 4-1 4.1.1 X Servers ................................ 4-1 4.1.1.1 X11R5 Xws Now Supports MX and PX ... 4-1 4.1.2 X Window System, Version 11 .............. 4-2 4.1.3 LinkWorks Components Have Been Retired and Renamed .................................... 4-2 4.2 UWS Notes ..................................... 4-3 4.2.1 Problems with the ~/DXterm Resource File . 4-3 5 Documentation 5.1 New Features and Changes ...................... 5-1 5.1.1 Hardcopy Documentation ................... 5-1 5.1.2 ULTRIX Online Reference Pages ............ 5-2 5.1.3 UWS Online Reference Pages ............... 5-2 5.1.4 ULTRIX Online Documentation CD-ROM Notes . 5-3 5.2 Documentation Notes ........................... 5-3 Contents v A Problems Resolved in Version 4.5 Tables 1-1: Media Labels for Version 4.5 .................. 1-5 1-2: Sizes of ULTRIX and UWS RISC Supported Subsets 1-8 1-3: Sizes of ULTRIX and UWS RISC Unsupported Subsets..1-10 1-4: Sizes of ULTRIX and UWS RISC Boot/Upgrade Subsets ....................................... 1-11 1-5: Sizes of ULTRIX and UWS RISC Encryption Kit Subsets ....................................... 1-12 1-6: Sizes of ULTRIX and UWS VAX Supported Subsets . 1-13 1-7: Sizes of ULTRIX and UWS VAX Unsupported Subsets . 1-15 1-8: Sizes of ULTRIX and UWS VAX Boot Upgrade Subsets..1-17 1-9: Sizes of ULTRIX and UWS VAX Encryption Kit Subsets ....................................... 1-17 1-10: Space Needed in RIS Areas .................... 1-18 A-1: ULTRIX Problems Resolved in Version 4.5 (A-F) . A-1 A-2: ULTRIX Problems Resolved in Version 4.5 (G-M) . A-12 A-3: ULTRIX Problems Resolved in Version 4.5 (N-R) . A-18 A-4: ULTRIX Problems Resolved in Version 4.5 (S-Z) . A-23 A-5: UWS Problems Resolved in Version 4.5 .......... A-32 vi Contents About This Manual This manual discusses the new features and changes in the ULTRIX and ULTRIX Worksystem Software Version 4.5 products. It also discusses any current issues, including problems discovered during the release and, where possible, their workarounds. Finally, tables in this manual describe the software problems that have been resolved by this release. Read Chapter 1 before you install or upgrade to ULTRIX and ULTRIX Worksystem Software Version 4.5. Read the rest of the notes before using the products. If you discover errors, omissions, or inaccuracies as you use the software and documentation, report the problem to your local Digital representative. _A_u_d_i_e_n_c_e This document is written for people who install, manage, and maintain ULTRIX and ULTRIX Worksystem Software (UWS) and their documentation. Also, programmers and other users of the ULTRIX and UWS software will find in these release notes information that affects their work. _O_r_g_a_n_i_z_a_t_i_o_n This document contains five chapters and one appendix: Chapter 1 Contains information about the installation and upgrade, including new features, changes since the last version, and known issues or problems. Chapter 2 Contains information about the hardware, including new features, changes since the last version, and known issues or problems. Chapter 3 Contains information about the ULTRIX software components, including new features, changes since the last version, and known issues or problems. Chapter 4 Contains information about the ULTRIX Worksystem Software (UWS) software components, including new features, changes since the last version, and known issues or problems. Chapter 5 Contains information about the the ULTRIX and UWS documentation, including new features, changes since the last version, and known issues or problems. Appendix A Contains tables that define which software problems have been resolved by this release. _R_e_l_a_t_e_d _D_o_c_u_m_e_n_t_a_t_i_o_n You should have the ULTRIX and UWS documentation kit and your hardware documentation. In addition to this document, the documents most likely to help you get started are: +o _U_L_T_R_I_X _a_n_d _U_W_S _V_e_r_s_i_o_n _4._5 _S_o_f_t_w_a_r_e _P_r_o_d_u_c_t _D_e_s_c_r_i_p_t_i_o_n_s (SPDs) The SPDs contain the legal definition of the software products. +o _U_L_T_R_I_X _a_n_d _U_W_S _V_e_r_s_i_o_n _4._5 _S_y_s_t_e_m _N_o_t_e_s These notes contain information from previous release notes that still is relevant to the current version of the products. +o _G_u_i_d_e _t_o _I_n_s_t_a_l_l_i_n_g _U_L_T_R_I_X _a_n_d _U_W_S This guide steps you through installations and upgrades of ULTRIX and UWS. +o _G_u_i_d_e _t_o _S_y_s_t_e_m _a_n_d _N_e_t_w_o_r_k _S_e_t_u_p This guide defines the tasks you perform after installing or upgrading ULTRIX and UWS. +o _G_u_i_d_e _t_o _S_h_a_r_i_n_g _S_o_f_t_w_a_r_e _o_n _a _L_o_c_a_l _A_r_e_a _N_e_t_w_o_r_k This guide steps you through the Remote Installation Services (RIS) and the Diskless Management Services (DMS) for ULTRIX and UWS. viii About This Manual _C_o_n_v_e_n_t_i_o_n_s % A percent sign represents the C shell $ system prompt. A dollar sign represents the system prompt for the Bourne and Korn shells. # A number sign represents the superuser prompt. % cat Boldface type in interactive examples indicates typed user input. file Italic (slanted) type indicates variable values, placeholders, and function argument names. . . . In syntax definitions, a horizontal ellipsis indicates that the preceding item can be repeated one or more times. _c_a_t(1) A cross-reference to a reference page includes the appropriate section number in parentheses. For example, _c_a_t(1) indicates that you can find information on the _c_a_t command in Section 1 of the reference pages. Ctrl/_x This symbol indicates that you hold down the first named key while pressing the key or mouse button that follows the slash. In examples, this key combination is enclosed in a box (for example, ). About This Manual ix Installation and Upgrade 1 The first section of this chapter discusses new features of and changes to the installation and upgrade procedures for the ULTRIX and ULTRIX Worksystem Software (UWS) products. The second section of this chapter discusses current issues for: +o Installation and upgrade procedures +o Software media and subsets +o Booting the system +o Configuring the system +o RIS and DMS +o After upgrade or installation Read this chapter before you install or upgrade the ULTRIX and UWS software. _1._1 _N_e_w _F_e_a_t_u_r_e_s _a_n_d _C_h_a_n_g_e_s There are no new features or changes to the products' installation or upgrade. _1._2 _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _U_p_g_r_a_d_e _N_o_t_e_s The following sections discuss current installation and upgrade issues. _1._2._1 _L_a_r_g_e_r _S_w_a_p _S_p_a_c_e _N_e_e_d_e_d With the addition of OSF/Motif Version 1.2, many of the UWS components have increased in size, and so require more swap space. The _G_u_i_d_e _t_o _I_n_s_t_a_l_l_i_n_g _U_L_T_R_I_X _a_n_d _U_W_S recommends creating a swap space that is three to four times the size of the processor's physical memory. If you plan to run the OSF/Motif user environment, you should create a swap space of this size. _1._2._2 _D_e_l_e_t_e _X_U_I _S_u_b_s_e_t_s _B_e_f_o_r_e _U_p_g_r_a_d_i_n_g _t_o _O_S_F/_M_o_t_i_f If you are upgrading a system with XUI subsets installed and you choose to put OSF/Motif on the new system instead of XUI, you should first shut down to single-user mode and remove the XUI subsets (using the _s_e_t_l_d -_d command). Otherwise, some files from the XUI subsets may be left on your system after the upgrade. _1._2._2._1 _D_o _N_o_t _A_p_p_l_y _P_r_e_v_i_o_u_s_l_y _P_u_b_l_i_s_h_e_d _P_a_t_c_h_e_s _t_o _V_e_r_s_i_o_n _4._5 If you have received any patches for ULTRIX and UWS Version 4.4 or earlier releases, do not install them after you have installed or upgraded to Version 4.5. The tables in Appendix A describe the patches that have been included in Version 4.5. If you have questions about patches, contact your local Digital representative. _1._2._2._2 _F_i_e_l_d _T_e_s_t _S_y_s_t_e_m_s _M_u_s_t _R_e_m_o_v_e _C_e_r_t_a_i_n _L_o_c_k _F_i_l_e_s _B_e_f_o_r_e _U_p_g_r_a_d_e If you have installed field test versions of ULTRIX and UWS Version 4.5 on your system and you plan to upgrade to another field test version, you must remove certain lock files before you perform the upgrade. The _s_e_t_l_d utility checks the lock files during an upgrade to determine which subsets are already installed. Failing to remove these lock files will cause the prerelease software to remain on the system rather than upgrading to the final product. You must remove the lock files before performing the upgrade. The steps are different for RISC and VAX systems. _1._2._2._2._1 _R_e_m_o_v_i_n_g _L_o_c_k _f_i_l_e_s _f_r_o_m _R_I_S_C _S_y_s_t_e_m_s - To remove unwanted lock files from RISC systems: 1. Bring the system to single-user mode by entering the following command: # /_e_t_c/_s_h_u_t_d_o_w_n '_n_o_w' 2. Change directory to the root file system by 1-2 Installation and Upgrade entering the following command: # _c_d / 3. If you have a DMS system, change directory to the DMS root environment. 4. Remove the lock files from the _u_s_r/_e_t_c/_s_u_b_s_e_t_s directories for supported commands: # _r_m _u_s_r/_e_t_c/_s_u_b_s_e_t_s/_U_D[_T_W]*_4_5?._l_k # _r_m _u_s_r/_e_t_c/_s_u_b_s_e_t_s/_D_X_M*_4_5?._l_k 5. If you are upgrading unsupported subsets, enter the command: # _r_m _u_s_r/_e_t_c/_s_u_b_s_e_t_s/_U_D_X*_4_5?._l_k 6. Follow the upgrade instructions in Chapter 5 of the _G_u_i_d_e _t_o _I_n_s_t_a_l_l_i_n_g _U_L_T_R_I_X _a_n_d _U_W_S. _1._2._2._2._2 _R_e_m_o_v_i_n_g _L_o_c_k _F_i_l_e_s _f_r_o_m _V_A_X _S_y_s_t_e_m_s - To remove unwanted lock files from VAX systems: 1. Change directory to the root file system by entering the following command: # _c_d / 2. If you have a DMS system, change directory to the DMS root environment. 3. Remove the lock files from the _u_s_r/_e_t_c/_s_u_b_s_e_t_s directories for supported commands: # _r_m _u_s_r/_e_t_c/_s_u_b_s_e_t_s/_U_L_T*_4_5?._l_k # _r_m _u_s_r/_e_t_c/_s_u_b_s_e_t_s/_U_W_S*_4_5?._l_k # _r_m _u_s_r/_e_t_c/_s_u_b_s_e_t_s/_D_X_V*_4_5?._l_k 4. If you are upgrading unsupported subsets, enter the command: # _r_m _u_s_r/_e_t_c/_s_u_b_s_e_t_s/_U_D_X*_4_5?._l_k 5. Follow the upgrade instructions in Chapter 5 of the _G_u_i_d_e _t_o _I_n_s_t_a_l_l_i_n_g _U_L_T_R_I_X _a_n_d _U_W_S. Installation and Upgrade 1-3 _1._2._2._3 _S_t_o_p_p_i_n_g _I_n_s_t_a_l_l_a_t_i_o_n _w_i_t_h _C_t_r_l/_C A full installation stops after you press Ctrl/C. You must restart the installation from the beginning. Depending on where you are in the installation procedure, you may see a display such as the following: Do you want to stop the installation? The installation will stop regardless of your answer to this question. _1._2._2._4 _L_o_a_d_i_n_g _S_o_f_t_w_a_r_e _U_p_d_a_t_e_s _D_u_r_i_n_g _a_n _U_p_g_r_a_d_e This release may include one or more software subsets that update (replace) components in the standard subsets included on the software kit. If you are upgrading your system from an earlier version of ULTRIX and UWS, be sure to install these updates to the subsets as explained in Section 5.1.6 of the _G_u_i_d_e _t_o _I_n_s_t_a_l_l_i_n_g _U_L_T_R_I_X _a_n_d _U_W_S. Failure to install these updates to subsets could cause system problems later. _1._2._2._5 _R_e_b_u_i_l_d_i_n_g _t_h_e _K_e_r_n_e_l _D_u_r_i_n_g _a_n _U_p_g_r_a_d_e Be sure to rebuild your kernel when upgrading your system to Version 4.5. Section 5.1.7 and Section 5.1.8 of the _G_u_i_d_e _t_o _I_n_s_t_a_l_l_i_n_g _U_L_T_R_I_X _a_n_d _U_W_S explain the steps needed to rebuild your kernel as part of the upgrade process. _1._2._3 _S_o_f_t_w_a_r_e _M_e_d_i_a _a_n_d _S_u_b_s_e_t_s The following notes discuss media and subsets issues. _1._2._3._1 _V_A_X _C_o_n_s_o_l_e _M_e_d_i_a _L_a_b_e_l_i_n_g _D_i_f_f_e_r_e_n_c_e_s Some of the VAX console media have not changed since Version 4.3. These media retain their Version 4.3 labels. The instructions in the _G_u_i_d_e _t_o _I_n_s_t_a_l_l_i_n_g _U_L_T_R_I_X _a_n_d _U_W_S take this into account. 1-4 Installation and Upgrade _1._2._3._2 _M_e_d_i_a _L_a_b_e_l_s Table 1-1 lists the media labels for Version 4.5. Table 1-1: _M_e_d_i_a _L_a_b_e_l_s _f_o_r _V_e_r_s_i_o_n _4._5 ______________________________________ Media Type Media Label ______________________________________ TK50 (RISC) ULTRIX AND UWS V4.5 (RISC) BOOT/UPGRADE ULTRIX AND UWS V4.5 (RISC) SUPPORTED SUBSETS VOLUME 1 ULTRIX AND UWS V4.5 (RISC) SUPPORTED SUBSETS VOLUME 2 ULTRIX AND UWS V4.5 (RISC) UNSUPPORTED SUBSETS ULTRIX AND UWS V4.5 (RISC) ENCRYPTION SUBSETS TK50 (VAX) ULTRIX AND UWS V4.5 (VAX) BOOT/UPGRADE ULTRIX AND UWS V4.5 (VAX) SUPPORTED SUBSETS ULTRIX AND UWS V4.5 (VAX) UNSUPPORTED SUBSETS ULTRIX AND UWS V4.5 (VAX) ENCRYPTION SUBSETS Installation and Upgrade 1-5 Table 1-1: (continued) ______________________________________ Media Type Media Label ______________________________________ MT9 (RISC) ULTRIX AND UWS V4.5 (RISC) BOOT/UPGRADE ULTRIX AND UWS V4.5 (RISC) SUPPORTED SUBSETS VOLUME 1 ULTRIX AND UWS V4.5 (RISC) SUPPORTED SUBSETS VOLUME 2 ULTRIX AND UWS V4.5 (RISC) SUPPORTED SUBSETS VOLUME 3 ULTRIX AND UWS V4.5 (RISC) SUPPORTED SUBSETS VOLUME 4 ULTRIX AND UWS V4.5 (RISC) UNSUPPORTED SUBSETS VOLUME 1 ULTRIX AND UWS V4.5 (RISC) UNSUPPORTED SUBSETS VOLUME 2 ULTRIX AND UWS V4.5 (RISC) ENCRYPTION SUBSETS 1-6 Installation and Upgrade Table 1-1: (continued) ______________________________________ Media Type Media Label ______________________________________ MT9 (VAX) ULTRIX AND UWS V4.5 (VAX) BOOT/UPGRADE ULTRIX AND UWS V4.5 (VAX) SUPPORTED SUBSETS VOLUME 1 ULTRIX AND UWS V4.5 (VAX) SUPPORTED SUBSETS VOLUME 2 ULTRIX AND UWS V4.5 (VAX) SUPPORTED SUBSETS VOLUME 3 ULTRIX AND UWS V4.5 (VAX) UNSUPPORTED SUBSETS VOLUME 1 ULTRIX AND UWS V4.5 (VAX) UNSUPPORTED SUBSETS VOLUME 2 ULTRIX AND UWS V4.5 (VAX) ENCRYPTION SUBSETS CD-ROM (RISC) ULTRIX AND UWS V4.5 SUPP/UNSUPP (RISC) Includes BOOT/UPGRADE ULTRIX AND UWS V4.5 RISC/VAX ENCRYPTION SUBSETS CD-ROM (VAX) ULTRIX AND UWS V4.5 (VAX) SUPP/UNSUPP (VAX) Includes BOOT/UPGRADE ULTRIX AND UWS V4.5 RISC/VAX ENCRYPTION SUBSETS ______________________________________ Installation and Upgrade 1-7 _1._2._3._3 _U_L_T_R_I_X _a_n_d _U_W_S _R_I_S_C _S_u_b_s_e_t _S_i_z_e_s The following sections list the subset sizes for the supported, the unsupported, the boot/upgrade, and the encryption subsets that make up ULTRIX and UWS Version 4.5. _N_o_t_e The actual subset sizes may vary from these numbers in the external product. These numbers approximate the final sizes: they are calculated from the field test software. For a description of each subset, see the _G_u_i_d_e _t_o _I_n_s_t_a_l_l_i_n_g _U_L_T_R_I_X _a_n_d _U_W_S. _1._2._3._3._1 _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _R_I_S_C _S_u_p_p_o_r_t_e_d _S_u_b_s_e_t_s - Table 1-2 lists the sizes of the supported ULTRIX and UWS RISC subsets in kilobytes for the root, /_u_s_r, and /_v_a_r directories. Table 1-2: _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _R_I_S_C _S_u_p_p_o_r_t_e_d _S_u_b_s_e_t_s _______________________________________________________________ Subset root /usr Size /var Total Size (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) _______________________________________________________________ DXMDECW450 -- 15998.300 -- 15998.300 DXMMAIL450 -- 5024.190 -- 5024.190 DXMMAN450 -- 4679.380 -- 4679.380 DXMX11450 -- 21471.800 -- 21471.800 DXMXDEVG0450 -- 8004.850 -- 8004.850 DXMXM450 -- 15540.700 -- 15540.700 UDT210PGMR450 -- 4.599 -- 4.599 UDTACCT450 0.043 249.856 -- 249.899 UDTAFM450 -- 901.603 -- 901.603 UDTBASE450 3155.290 25108.500 35.636 28299.400 UDTBGX450 -- 3980.570 -- 3980.570 1-8 Installation and Upgrade Table 1-2: (continued) _______________________________________________________________ Subset root /usr Size /var Total Size (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) _______________________________________________________________ UDTBIN450 13.252 38931.200 -- 38944.500 UDTCDABASE450 -- 7139.340 -- 7139.340 UDTCDAPGMR450 -- 1519.070 -- 1519.070 UDTCOMM450 13.728 1245.180 -- 1258.910 UDTDCMT450 0.017 290.438 -- 290.455 UDTDCMTEXT450 -- 1078.070 -- 1078.070 UDTDL450 78.811 3327.810 -- 3406.620 UDTEXAMPLES450 -- 1163.240 -- 1163.240 UDTEXER450 -- 954.473 -- 954.473 UDTINET450 452.065 5675.300 59.393 6186.760 UDTINTLPGMR450 -- 582.959 -- 582.959 UDTINTLRT450 -- 110.724 -- 110.724 UDTKERB450 -- 1233.630 756.884 1990.510 UDTMAN450 -- 3343.130 -- 3343.130 UDTMANPGMR450 -- 1459.810 -- 1459.810 UDTMH450 0.512 7754.830 1.024 7756.370 UDTMIPS3PGMR450 -- 3485.670 -- 3485.670 UDTMOP450 32.702 425.044 78.336 536.082 UDTNFS450 201.744 1439.330 541.170 2182.240 UDTPGMR450 0.040 10363.800 -- 10363.800 UDTPRESTO450 -- 163.840 0.539 164.379 UDTPRINT450 37.055 2682.910 0.512 2720.480 UDTRPCDEV450 -- 648.067 90.112 738.179 UDTRPCRT450 0.014 275.750 1338.780 1614.540 UDTSCCS450 -- 1194.310 -- 1194.310 UDTSEC450 377.783 935.539 -- 1313.320 UDTSMSCAMP450 -- 102.219 -- 102.219 UDTUMAIL450 62.507 895.195 -- 957.702 UDTUUCP450 0.020 612.534 997.897 1610.450 UDWDECW450 -- 11681.500 -- 11681.500 UDWFONT15450 -- 5612.330 -- 5612.330 Installation and Upgrade 1-9 Table 1-2: (continued) _______________________________________________________________ Subset root /usr Size /var Total Size (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) _______________________________________________________________ UDWFONT450 -- 4322.370 -- 4322.370 UDWFONTSTR450 -- 164.352 -- 164.352 UDWMAIL450 -- 2713.850 -- 2713.850 UDWMAN450 -- 364.243 -- 364.243 UDWMANPGMR450 -- 1562.800 -- 1562.800 UDWSER450 -- 12292.500 56.739 12349.200 UDWSYSMGNT450 -- 3090.640 -- 3090.640 UDWWSTSER450 -- 2740.570 -- 2740.570 UDWX11450 -- 6075.160 -- 6075.160 UDWXDEV450 -- 8508.400 -- 8508.400 UDWXTXSER450 -- 5281.810 -- 5281.810 TOTALS 4425.580 264408.000 3957.020 272791.000 _______________________________________________________________ _1._2._3._3._2 _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _R_I_S_C _U_n_s_u_p_p_o_r_t_e_d _S_u_b_s_e_t_s - Table 1-3 lists the sizes of the unsupported ULTRIX and UWS RISC subsets in kilobytes for the root, /_u_s_r, and /_v_a_r directories. Table 1-3: _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _R_I_S_C _U_n_s_u_p_p_o_r_t_e_d _S_u_b_s_e_t_s ___________________________________________________________ Subset root /usr Size /var Total Size (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) ___________________________________________________________ DXMUNDEMO450 -- 4523.520 -- 4523.520 UDXBASE450 0.192 3238.700 0.512 3239.400 UDXBIB450 -- 291.745 -- 291.745 UDXCOURIER450 -- 160.374 -- 160.374 1-10 Installation and Upgrade Table 1-3: (continued) ___________________________________________________________ Subset root /usr Size /var Total Size (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) ___________________________________________________________ UDXDCMT450 -- 391.685 -- 391.685 UDXDOC450 -- 3447.050 -- 3447.050 UDXEDIT450 -- 6328.980 -- 6328.980 UDXGAMES450 -- 2453.760 -- 2453.760 UDXINET450 86.068 828.573 -- 914.641 UDXLEARN450 -- 723.837 -- 723.837 UDXMAN450 -- 175.436 -- 175.436 UDXNEWS450 -- 1326.030 -- 1326.030 UDXNOTES450 -- 1827.580 -- 1827.580 UDXRCS450 -- 528.940 -- 528.940 UDXSHELLS450 -- 85.968 -- 85.968 UDXTERM450 -- 324.438 -- 324.438 UDXTOOLS450 -- 115.650 -- 115.650 UDXUNEXAMP450 -- 1054.740 -- 1054.740 UDXUNFONTS450 -- 13740.100 -- 13740.100 UDXUNMAN450 -- 652.310 -- 652.310 UDXUNMIT450 -- 34403.200 -- 34403.200 TOTALS 86.260 76622.600 0.512 76709.400 ___________________________________________________________ _1._2._3._3._3 _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _R_I_S_C _B_o_o_t _U_p_g_r_a_d_e _S_u_b_s_e_t_s - Table 1-4 lists the sizes of the RISC boot/upgrade subsets in kilobytes for the root, /_u_s_r, and /_v_a_r directories. Table 1-4: _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _R_I_S_C _B_o_o_t/_U_p_g_r_a_d_e _S_u_b_s_e_t_s _____________________________________________________________ Subset root Size Installation and Upgrade 1-11 Table 1-4: (continued) _____________________________________________________________ Subset root /usr Size /var Total Size (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) ______________________________/_u_s_r__S_i_z_e____/_v_a_r_________T _o_t_a_l___ (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) _____________________________________________________________ DXMSYSMGNT450 -- 3911.780 -- 3911.780 UDTBASE451 -- 1597.820 -- 1597.820 UDTBGX451 -- 456.560 -- 456.560 UDTBIN451 -- 65.534 -- 65.534 UDTGENVMUNIX451 -- 3236.610 -- 3236.610 UDTMIPS3PGMR451 -- 3249.650 -- 3249.650 UDTPGMR451 -- 3249.300 -- 3249.300 TOTALS -- 15767.300 -- 15767.300 _____________________________________________________________ _1._2._3._3._4 _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _R_I_S_C _E_n_c_r_y_p_t_i_o_n _K_i_t _S_u_b_s_e_t_s - Table 1-5 lists the sizes of the Encryption Kit subsets in kiloybtes for the root, the /_u_s_r, and /_v_a_r directories. Table 1-5: _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _R_I_S_C _E_n_c_r_y_p_t_i_o_n _K_i_t _S_u_b_s_e_t_s _______________________________________________________ Subset root /usr /var Total Size Size Size (Kbytes) (Kbytes) (Kbytes) (Kbytes) _______________________________________________________ UDCCRYPT450 -- 614.400 0.538 614.938 UDCPGMR450 -- 1656.620 -- 1656.620 TOTALS -- 2271.020 0.538 2271.560 _______________________________________________________ 1-12 Installation and Upgrade _1._2._3._4 _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _V_A_X _S_u_b_s_e_t_s The following sections list the sizes of the supported, the unsupported, the boot/upgrade, and the encryption subsets that make up ULTRIX and UWS Version 4.5. _N_o_t_e The actual subset sizes may vary from these numbers in the external product. These numbers approximate the final sizes: they are calculated from the field test software. _1._2._3._4._1 _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _V_A_X _S_u_p_p_o_r_t_e_d _S_u_b_s_e_t_s - Table 1-6 lists the sizes of VAX supported ULTRIX and UWS subsets in kilobytes for the root, /_u_s_r, and /_v_a_r directories. Table 1-6: _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _V_A_X _S_u_p_p_o_r_t_e_d _S_u_b_s_e_t_s ______________________________________________________________ Subset root /usr Size /var Total Size (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) ______________________________________________________________ DXVDECW450 -- 11964.700 -- 11964.700 DXVMAIL450 -- 3523.000 -- 3523.000 DXVMAN450 -- 4679.380 -- 4679.380 DXVX11450 -- 16439.800 -- 16439.800 DXVXM450 -- 8841.810 -- 8841.810 ULTACCT450 0.043 143.360 -- 143.403 ULTAFM450 -- 901.603 -- 901.603 ULTBASE450 2049.090 10753.400 36.148 12838.600 ULTBIN450 13.251 7259.620 -- 7272.870 ULTBSC450 0.036 209.920 -- 209.956 ULTCDABASE450 -- 5367.820 -- 5367.820 ULTCDAPGMR450 -- 1121.350 -- 1121.350 ULTCOMM450 13.728 759.808 -- 773.536 ULTDCMT450 0.017 187.868 -- 187.885 Installation and Upgrade 1-13 Table 1-6: (continued) ______________________________________________________________ Subset root /usr Size /var Total Size (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) ______________________________________________________________ ULTDCMTEXT450 -- 749.206 -- 749.206 ULTDL450 47.067 1657.410 -- 1704.480 ULTEXAMPLES450 -- 718.950 -- 718.950 ULTEXER450 -- 589.221 -- 589.221 ULTINET450 291.297 3487.650 107.521 3886.470 ULTINTLPGMR450 -- 326.715 -- 326.715 ULTINTLRT450 -- 110.724 -- 110.724 ULTKERB450 -- 933.634 539.796 1473.430 ULTMAN450 -- 3579.130 -- 3579.130 ULTMANPGMR450 -- 1279.360 -- 1279.360 ULTMH450 0.512 4868.170 1.024 4869.710 ULTMOP450 32.702 228.436 49.716 310.854 ULTNFS450 113.680 832.100 258.546 1204.330 ULTPASCAL450 -- 720.861 -- 720.861 ULTPGMR450 0.040 3765.640 -- 3765.680 ULTPRESTO450 -- 97.280 0.539 97.819 ULTPRINT450 16.575 2069.640 0.512 2086.730 ULTRPCDEV450 -- 457.109 53.248 510.357 ULTRPCRT450 0.014 275.750 871.841 1147.600 ULTSCCS450 -- 720.185 -- 720.185 ULTSEC450 256.951 575.091 -- 832.042 ULTSMSCAMP450 -- 102.219 -- 102.219 ULTUMAIL450 62.507 616.912 -- 679.419 ULTUUCP450 0.020 366.774 631.305 998.099 ULTVAXC450 -- 878.598 -- 878.598 UWS3DFONT450 -- 3922.590 -- 3922.590 UWSDECW450 -- 9143.050 -- 9143.050 UWSFONT15450 -- 3955.250 -- 3955.250 UWSFONT450 -- 2918.010 -- 2918.010 UWSMAIL450 -- 1733.880 -- 1733.880 UWSMAN450 -- 364.243 -- 364.243 1-14 Installation and Upgrade Table 1-6: (continued) ______________________________________________________________ Subset root /usr Size /var Total Size (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) ______________________________________________________________ UWSMANPGMR450 -- 1562.800 -- 1562.800 UWSSER450 -- 7344.430 56.739 7401.170 UWSSYSMGNT450 -- 2237.650 -- 2237.650 UWSX11450 -- 4313.880 -- 4313.880 UWSXDEV450 -- 4598.340 -- 4598.340 TOTALS 2897.530 144254.000 2606.940 149759.000 ______________________________________________________________ _1._2._3._4._2 _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _V_A_X _U_n_s_u_p_p_o_r_t_e_d _S_u_b_s_e_t_s - Table 1-7 lists the sizes of the unsupported ULTRIX and UWS VAX subsets in kilobytes for the root, /_u_s_r, and /_v_a_r directories. Table 1-7: _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _V_A_X _U_n_s_u_p_p_o_r_t_e_d _S_u_b_s_e_t_s ___________________________________________________________ Subset root /usr Size /var Total Size (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) ___________________________________________________________ DXVUNDEMO450 -- 4115.760 -- 4115.760 ULXAPL450 -- 269.805 -- 269.805 ULXBASE450 1.511 1959.670 0.512 1961.690 ULXBIB450 -- 194.057 -- 194.057 ULXCOURIER450 -- 103.618 -- 103.618 ULXCPM450 -- 28.934 -- 28.934 ULXDCMT450 -- 368.336 -- 368.336 ULXDOC450 -- 3447.050 -- 3447.050 ULXEDIT450 -- 6328.980 -- 6328.980 ULXF77450 -- 732.618 -- 732.618 Installation and Upgrade 1-15 Table 1-7: (continued) ___________________________________________________________ Subset root /usr Size /var Total Size (Kbytes) Size (Kbytes) (Kbytes) (Kbytes) ___________________________________________________________ ULXGAMES450 -- 2223.420 -- 2223.420 ULXHYPER450 -- 80.771 -- 80.771 ULXICON450 -- 346.396 -- 346.396 ULXINET450 52.276 450.230 -- 502.506 ULXINGRES450 -- 2608.420 -- 2608.420 ULXLEARN450 -- 652.284 -- 652.284 ULXLISP450 -- 3216.460 -- 3216.460 ULXMAN450 -- 310.709 -- 310.709 ULXMOD2450 -- 1035.540 -- 1035.540 ULXNEWS450 -- 1326.030 -- 1326.030 ULXNOTES450 -- 1176.320 -- 1176.320 ULXRCS450 -- 543.056 -- 543.056 ULXSHELLS450 -- 54.224 -- 54.224 ULXSPMS450 -- 1213.530 -- 1213.530 ULXTERM450 -- 324.438 -- 324.438 ULXTOOLS450 -- 54.210 -- 54.210 ULXUNEXAMP450 -- 1054.120 -- 1054.120 ULXUNFONTS450 -- 9838.670 -- 9838.670 ULXUNMAN450 -- 652.310 -- 652.310 ULXUNMIT450 -- 21926.800 -- 21926.800 ULXVARIAN450 -- 2736.110 -- 2736.110 TOTALS 53.787 69372.900 0.512 69427.200 ___________________________________________________________ _1._2._3._4._3 _S_i_z_e_s _o_f _V_A_X _B_o_o_t _U_p_g_r_a_d_e _S_u_b_s_e_t_s - Table 1-8 lists the sizes of the VAX boot/upgrade subsets in kilobytes for the root, /_u_s_r, and /_v_a_r directories. 1-16 Installation and Upgrade Table 1-8: _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _V_A_X _B_o_o_t _U_p_g_r_a_d_e _S_u_b_s_e_t_s ___________________________________________________________ Subset root /usr /var Total Size Size Size (Kbytes) (Kbytes) (Kbytes) (Kbytes) ___________________________________________________________ DXVSYSMGNT450 -- 2814.980 -- 2814.980 ULTBASE451 -- 382.530 -- 382.530 ULTBIN451 -- 11.055 -- 11.055 ULTGENVMUNIX451 -- 1581.060 -- 1581.060 ULTPGMR451 -- 1188.670 -- 1188.670 TOTALS -- 5978.300 -- 5978.300 ___________________________________________________________ _1._2._3._4._4 _S_i_z_e_s _o_f _V_A_X _E_n_c_r_y_p_t_i_o_n _K_i_t _S_u_b_s_e_t_s - Table 1-9 lists the sizes of the VAX Encryption Kit subsets in kilobytes for the root, /_u_s_r, and /_v_a_r directories. Table 1-9: _S_i_z_e_s _o_f _U_L_T_R_I_X _a_n_d _U_W_S _V_A_X _E_n_c_r_y_p_t_i_o_n _K_i_t _S_u_b_s_e_t_s _______________________________________________________ Subset root /usr /var Total Size Size Size (Kbytes) (Kbytes) (Kbytes) (Kbytes) _______________________________________________________ ULCCRYPT450 -- 376.832 0.538 377.370 ULCPGMR450 -- 1268.590 -- 1268.590 TOTALS -- 1645.420 0.538 1645.960 _______________________________________________________ _1._2._4 _B_o_o_t_i_n_g _t_h_e _S_y_s_t_e_m There are no system boot issues. Installation and Upgrade 1-17 _1._2._5 _R_I_S _a_n_d _D_M_S _N_o_t_e_s The following notes pertain to RIS and DMS. _1._2._5._1 _U_L_T_R_I_X _R_I_S _S_e_r_v_e_r_s _a_n_d _D_i_g_i_t_a_l _U_N_I_X _C_l_i_e_n_t_s The capability of a ULTRIX RIS server to support and serve Digital UNIX clients is to be retired with this release of the ULTRIX operating system. _1._2._5._2 _S_p_a_c_e _N_e_e_d_e_d _t_o _I_n_s_t_a_l_l _U_L_T_R_I_X _a_n_d _U_W_S _i_n _R_I_S _a_n_d _D_M_S _A_r_e_a_s Table 1-10 lists the space (in kilobytes) needed to install the Version 4.5 subsets in a RIS area. Table 1-10: _S_p_a_c_e _N_e_e_d_e_d _i_n _R_I_S _A_r_e_a_s _____________________________________________________________ Component RISC Space (kilobytes) VAX Space (kilobytes) _____________________________________________________________ BOOT/UPGRADE 20635 7931 Supported 131108 79362 Unsupported 49069 49443 Encryption 2266 1666 _____________________________________________________________ Instructions for determining the size of a DMS area are contained in the _G_u_i_d_e _t_o _S_h_a_r_i_n_g _S_o_f_t_w_a_r_e _o_n _a _L_o_c_a_l _A_r_e_a _N_e_t_w_o_r_k. The approximate sizes of the software subsets for Version 4.5 are shown in the tables earlier in this chapter. _1._2._5._3 _D_M_S _M_o_d_i_f_y _O_p_t_i_o_n _C_o_u_l_d _F_a_i_l _w_i_t_h _C_l_i_e_n_t _o_n _D_i_f_f_e_r_e_n_t _S_u_b_n_e_t The DMS Modify option could fail to modify a client system that is on a subnet different from the server system. The symptom of this failure is a client system panic during its boot process. To work around the problem, you must compile a new version of the client's _n_e_t_b_l_k._c file, then reboot the client. 1-18 Installation and Upgrade From the server system, take the following steps: 1. As superuser, locate the client's /_d_l_c_l_i_e_n_t?/_h_o_s_t_n_a_m_e._r_o_o_t/_e_t_c directory, substituting the name of the client for _h_o_s_t_n_a_m_e: # _f_i_n_d /_d_l_c_l_i_e_n_t? -_n_a_m_e _h_o_s_t_n_a_m_e._r_o_o_t -_p_r_i_n_t 2. Change directory to the client's /_d_l_c_l_i_e_n_t?/_h_o_s_t_n_a_m_e._r_o_o_t/_e_t_c directory. 3. Compile the _n_e_t_b_l_k._c file. For example: # _c_c -_c _n_e_t_b_l_k._c 4. After the file _n_e_t_b_l_k._c has been compiled to produce file _n_e_t_b_l_k._o, reboot the client system. _1._2._6 _A_f_t_e_r _t_h_e _U_p_g_r_a_d_e _o_r _I_n_s_t_a_l_l_a_t_i_o_n The following sections pertain to tasks you can perform after you complete the upgrade or installation. _1._2._6._1 _C_h_a_n_g_e _t_h_e _d_i_s_k_t_a_b _F_i_l_e _a_f_t_e_r _A_l_l _U_p_g_r_a_d_e_s To acquire any new device support in ULTRIX and UWS Version 4.5, after an upgrade, you must change the _d_i_s_k_t_a_b file. This task is required when you upgrade a system. Do not perform this task when you install a system. After you have rebooted the new kernel to complete the upgrade, and before you delete any files, perform the following steps: 1. Save a copy of the /_e_t_c/_d_i_s_k_t_a_b file by copying it to another file. For example: # _c_p /_e_t_c/_d_i_s_k_t_a_b /_e_t_c/_d_i_s_k_t_a_b._s_a_v 2. Copy the upgrade procedure file /_e_t_c/._n_e_w.._d_i_s_k_t_a_b to /_e_t_c/_d_i_s_k_t_a_b, by using the following command: # _c_p /_e_t_c/._n_e_w.._d_i_s_k_t_a_b /_e_t_c/_d_i_s_k_t_a_b 3. If you have customized the previous /_e_t_c/_d_i_s_k_t_a_b Installation and Upgrade 1-19 file, you can use the copy you have saved to edit these customizations into the new /_e_t_c/_d_i_s_k_t_a_b file. _1._2._6._2 _E_n_s_u_r_i_n_g _t_h_a_t _l_o_c_k_d _a_n_d _s_t_a_t_d _a_r_e _R_u_n_n_i_n_g After upgrading your server to Version 4.5, make sure that _l_o_c_k_d and _s_t_a_t_d are running and included in the server's /_e_t_c/_r_c._l_o_c_a_l file. If these daemons are not running, you may not be able to boot your _r_i_s or _d_m_s clients. _1._2._6._3 _R_e_m_o_v_i_n_g "_p_r_o_t_o" _F_i_l_e_s _A_f_t_e_r _I_n_s_t_a_l_l _o_r _U_p_g_r_a_d_e When you install or upgrade your system to Version 4.5, certain customizable files, such as _d_i_s_k_t_a_b, are first installed with the prefix ._p_r_o_t_o.. and then copied to their actual file names. For example, the _d_i_s_k_t_a_b file is ._p_r_o_t_o.._d_i_s_k_t_a_b. These "proto" files are not deleted by the installation or upgrade procedures. These files are not needed. You can delete them once your installation or upgrade is complete. _1._2._6._4 _D_e_l_e_t_i_n_g _g_e_n_v_m_u_n_i_x _A_f_t_e_r _a_n _I_n_s_t_a_l_l_a_t_i_o_n After a Version 4.5 system is installed, you can delete the subset containing _g_e_n_v_m_u_n_i_x to save space. Use the _s_e_t_l_d command to delete the subset UDTGENVMUNIX451 for RISC systems, the subset ULTGENVMUNIX451 for VAX systems. Additionally, you can delete the /_u_s_r/_g_e_n_v_m_u_n_i_x file after you have copied it to /_g_e_n_v_m_u_n_i_x at the conclusion of an installation. _1._2._6._5 _D_e_l_e_t_e _L_o_c_k _F_i_l_e_s _W_h_e_n _R_e_c_o_n_f_i_g_u_r_i_n_g _f_r_o_m _M_o_t_i_f _t_o _X_U_I If you reconfigure your system to change your DECwindows user interface environment from OSF/Motif to XUI, you must delete a lock file that is not automatically deleted. Whenever you delete the DXMXM450 (RISC) or DXVXM450 (VAX) subset, you must also delete the lock file /_u_s_r/_e_t_c/_s_u_b_s_e_t_s/_U_D_W_X_D_E_V_4_5_0._l_k (for RISC systems) or the file /_u_s_r/_e_t_c/_s_u_b_s_e_t_s/_U_W_S_X_D_E_V_4_5_0._l_k (for VAX 1-20 Installation and Upgrade systems). If you do not delete the lock file, you will be unable install the UDWXDEV450 (RISC) or UWSXDEV450 (VAX) subset. The procedure checks for the lock file and, when found, assumes the subset is already installed. _1._2._7 _S_u_b_s_e_t _C_h_a_n_g_e_s This section discusses subset kitting changes for this version. _1._2._7._1 _S_y_s_t_e_m _M_a_n_a_g_e_m_e_n_t _S_u_b_s_e_t _C_h_a_n_g_e_s In earlier versions, the UDWSYSMGNT subsets did not take into account that there are two versions of _d_x_p_r_e_s_t_o, one for the XUI interface and one for the Motif interface. Regardless of which interface you chose during installation, you obtained the _d_x_p_r_e_s_t_o for the XUI interface. A new subset, DXMSYSMGNT/DXVSYSMGNT for the Motif interface has been added to the kit. The system management subsets are now split into two subsets, one for the XUI interface and one for the Motif interface. _1._2._7._2 _P_r_o_t_o_t_y_p_e _S_u_b_s_e_t _f_o_r _R_I_S_C _S_y_s_t_e_m_s A prototype subset has been added to the kit for RISC systems only. The subset is identified as: UDTBGX450 Prototype bind, gated, xnpt Utilities Installation and Upgrade 1-21 Hardware 2 There are no new hardware features for this release. ULTRIX and UWS Version 4.5 supports all of the configurations -- processors, graphics options, disks, tapes, and so on -- supported in Version 4.4 and earlier versions. There are no current hardware issues for processors, graphics options, or peripheral devices. For a complete list of hardware devices supported in ULTRIX and UWS, see the _U_L_T_R_I_X _V_e_r_s_i_o_n _4._5 _S_o_f_t_w_a_r_e _P_r_o_d_u_c_t _D_e_s_c_r_i_p_t_i_o_n (SPD). ULTRIX Software 3 The first section in this chapter discusses new features of and changes to the ULTRIX software components. The second section in this chapter contains notes that discuss current ULTRIX software issues, if any exist, for the following topics: +o Conformance to standards and external specifications +o Commands and utilities +o System calls +o Library routines +o Software development +o Printing +o Networks and communications +o SCSI/CAM _3._1 _N_e_w _F_e_a_t_u_r_e_s _a_n_d _C_h_a_n_g_e_s There are some small changes in the ULTRIX software. _3._1._1 _N_e_w _O_p_t_i_o_n _t_o _p_a_r_a_m._c _F_i_l_e An option to the _p_a_r_a_m._c file has been added. The option is _u_s_r_s_m_s, a configurable parameter which is the address that defines the lower boundary of the shared memory segments allocated above the stack segment. No shared memory segments are allowed to be in the address space between _u_s_r_s_m_s and the start of the user stack segment. The default value of _u_s_r_s_m_s is (unsigned) 0x60000000, which applies to each process using shared memory. Using a larger number, for example 0x70000000, makes available more space for the shared memory segments of a process, but reduces space for its stack growth. (The user stack segment starts at an address around 0x7fffc000 and grows towards the data segment and shared memory segments, if any.) Therefore, Digital recommends that you do not use a number for _u_s_e_r_s_m_s that is significantly larger than 0x60000000 unless a process requires an unusually large amount of shared memory. _3._1._2 _N_e_w _y_p_s_e_r_v(_8_y_p) _C_o_m_m_a_n_d _O_p_t_i_o_n A new option, -_l, has been added to the _y_p_s_e_r_v_e command. This option turns on log messages. Related _p_o_r_t_m_a_p messages are logged to the /_v_a_r/_y_p/_p_o_r_t_m_a_p._l_o_g file. Related _y_p_s_e_r_v messages are logged to the /_v_a_r/_y_p/_y_p_s_e_r_v._l_o_g file. Any fatal errors, such as not being able to open the /_e_t_c/_s_e_c_u_r_e_n_e_t_s file, or access denials are logged to _s_t_d_o_u_t. Any access denials to remote hosts are logged to the /_v_a_r/_y_p/_p_o_r_t_m_a_p._l_o_g file. Grants of permission to access resources are logged to the /_v_a_r/_y_p/_y_p_s_e_r_v._l_o_g file. If a SIGUSR1 signal is sent to either portmap or ypserv, the logging state toggles. _3._1._2._1 _N_e_w _Y_P _C_o_n_t_r_o_l _F_i_l_e The control file /_e_t_c/_s_e_c_u_r_e_n_e_t_s has been added. This file specifies which YP clients are permitted to request maps. You must configure the /_e_t_c/_s_e_c_u_r_e_n_e_t_s file to reflect the domain(s) where it is installed. The file consists of entries with a net mask and a net address. You must specify in this file all the physical networks, subnets, and specific hosts that need to communicate with either the portmapper or the YP server. For example, if your domains are defined as the following: 255.255.0.0 134.200.0.0 # all the hosts on the network 130.200 are allowed. 255.255.255.0 134.210.23.0 # all the hosts on the sub-net 130.210.23 are allowed. 255.255.255.0 134.220.23.14 # The specific host with the IP 130.220.23.14 is allowed. The /_e_t_c/_s_e_c_u_r_e_n_e_t_s file for the previous domains would contain the following entries: #This file contains the domain mask and addresses that are #allowed to receive maps from ypserv and ypxfr and may do #RPC programs against portmap. #format(the first entry is netmask, and the second entry is netaddr) 255.255.255.255 130.200.96.49 255.255.255.255 130.200.96.12 255.255.0.0 130.201.96.0 3-2 ULTRIX Software _3._2 _U_L_T_R_I_X _N_o_t_e_s The following sections contain notes about the ULTRIX software. _3._2._1 _P_r_i_n_t_i_n_g _N_o_t_e_s The following sections discuss printing issues. _3._2._1._1 _T_h_e _l_p_r_s_e_t_u_p _C_o_m_m_a_n_d When using the _l_p_r_s_e_t_u_p command to remove an entry from the _p_r_i_n_t_c_a_p file, the comments associated with the entry are not removed. If you want to remove the comments, you must edit the file. After using the _l_p_r_s_e_t_u_p command, the DEClaser 2200 and DEClaser 3200 printers require an additional change to select the default tray. You must add +_I<_t_r_a_y> after the input and output filter specification in the _p_r_i_n_t_c_a_p file. The <_t_r_a_y> is replaced with one of the _l_p_r command tray specifications of top, middle, bottom, or _l_c_i_t. No space should exist between the +I and the tray name. For example: :if=/usr/lib/lpdfilters/DECprinter +Itop: :of=/usr/lib/lpdfilters/DECprinter +Itop: _3._2._1._2 _T_h_e _D_E_C_p_r_i_n_t_e_r _P_r_i_n_t _F_i_l_t_e_r You can now specify in the _p_r_i_n_t_c_a_p file the default tray for the DEClaser 2200 and 3200 printers. For example: :if=/usr/lib/lpdfilters/ln03of +Itop: :of=/usr/lib/lpdfilters/ln03of +Itop: Existing _p_c_f files that were edited to specify the default trays will still work. The DECprinter filter was designed to switch automatically to landscape mode when the width of a document exceeded a specific column position as specified in the _p_c_f file. This feature did not work correctly in Version 4.4 and has not been corrected. To work around the problem, edit the _p_c_f file to change the `landscape width:' value to 0. For example, change _l_a_n_d_s_c_a_p_e _w_i_d_t_h:_8_1 to _l_a_n_d_s_c_a_p_e _w_i_d_t_h:_0. ULTRIX Software 3-3 The filter has been modified to recognize the following _l_p_r options: _l_p_r -_D_o_d_d and _l_p_r -_D_e_v_e_n. 3-4 ULTRIX Software ULTRIX Worksystem Software 4 The first section of this chapter discusses new features of and changes to the UWS software components. The second section of this chapter contains UWS system notes, if any exist, for the following topics: +o Standards and compatibility +o X Servers +o User environment +o OSF/Motif _4._1 _N_e_w _F_e_a_t_u_r_e_s _a_n_d _C_h_a_n_g_e_s The following sections discuss new features of and changes to this release. _4._1._1 _X _S_e_r_v_e_r_s The following sections discuss new features of and changes to the X servers. _4._1._1._1 _X_1_1_R_5 _X_w_s _N_o_w _S_u_p_p_o_r_t_s _M_X _a_n_d _P_X The _X_w_s X11R5 X server now supports the MX (PMAG-AA) and PX (PMAG-CA) graphic options. All of the graphics options that _X_w_s supported in Version 4.4 remain supported. If you are upgrading from Version 4.4 and you have an MX or PX graphics option, edit the /_e_t_c/_t_t_y_s file to change the X server name from _X_w_s__R_4 to _X_w_s in the following line: 0: "/usr/bin/login -P /usr/bin/Xprompter -C /usr/bin/dxsession" none on secure window="/usr/bin/Xws bc -once" The installation or upgrade procedure edits the /_e_t_c/_t_t_y_s file on your system to start the correct X server. To determine the graphics option on your system, become superuser and enter the /_e_t_c/_s_i_z_e_r -_g_t command on RISC systems or the /_e_t_c/_s_i_z_e_r -_w_t command on VAX systems. Whether you run an X11R4 or X11R5 X server depends solely upon the graphics option you have. It does not depend upon or affect whether you are running the X11R4 XUI environment or the X11R5 OSF/Motif environment. If you wish, you may run the X11R4 X servers ( _X_w_s__R_4 or _X_t_x__R_4 ) on systems that would normally use the X11R5 X servers ( _X_w_s or _X_t_x ). The X11R4 and X11R5 X servers support the same fonts, with one exception. The X11R5 X servers support scaled fonts and the X11R4 servers do not support scaled fonts. _4._1._2 _X _W_i_n_d_o_w _S_y_s_t_e_m, _V_e_r_s_i_o_n _1_1 There are no new features or changes to X Window System support. _4._1._3 _L_i_n_k_W_o_r_k_s _C_o_m_p_o_n_e_n_t_s _H_a_v_e _B_e_e_n _R_e_t_i_r_e_d _a_n_d _R_e_n_a_m_e_d The LinkWorks components, _l_w_k_m_a_n_a_g_e_r and _l_w_k_s_e_t_u_p, along with their associated libraries, have been retired. In Version 4.4, the source files for the LinkWorks components were removed from the UWS source kit. In Version 4.5, the LinkWorks binary files have been removed from the UWS binary kit. The name "LinkWorks" is now used for a new product with a different function. The retiring LinkWorks components have been renamed DEClinks. As a result, the user interface to the present LinkWorks capability, which allows users of applications to create links to other applications, is no longer present in ULTRIX and UWS. The DECwindows applications that used DEClinks (Bookreader, Cardfiler, and Calendar) have been modified to remove that feature. Applications that link against the DEClinks library /_u_s_r/_l_i_b/_l_i_b_l_w_k_d_x_m._a, need to be modified before they can be built on ULTRIX/UWS Version 4.5, because the DEClinks library is no longer provided. 4-2 ULTRIX Worksystem Software Applications that use DEClinks and which were built on an earlier version of ULTRIX can be run on Version 4.5: however, the DEClinks functions are no longer supported and do not work. _4._2 _U_W_S _N_o_t_e_s The following notes discuss UWS software issues. _4._2._1 _P_r_o_b_l_e_m_s _w_i_t_h _t_h_e ~/_D_X_t_e_r_m _R_e_s_o_u_r_c_e _F_i_l_e When you use the Save Options menu item, _d_x_t_e_r_m saves its entire resource database to a file named _D_X_t_e_r_m in your home directory. This can cause problems in the following situations: +o You use _d_x_t_e_r_m on screens with different depths +o You try to override some settings in the resource file with command line switches +o You use the -_s_e_t_u_p " switch to prevent ~/_D_X_t_e_r_m from being read To avoid these problems, do the following when using _d_x_t_e_r_m resource files: 1. Do not use the Save Options menu item to create the resource file. Use it only to determine the resource names and default values. 2. Edit the resource file manually to only contain the resources that are different than the system default values. 3. Use an alternate to having a ~/_D_X_t_e_r_m. Specify the alternate resource file name with the -_s_e_t_u_p switch. Or, use the -_x_r_m switch to specify any resources you want to change. ULTRIX Worksystem Software 4-3 Documentation 5 The first section of this chapter discusses new features of and changes to the ULTRIX and UWS hardcopy documentation, online reference pages, and online documentation CD-ROM. The second section of this chapter discusses any current documentation issues or problems. _5._1 _N_e_w _F_e_a_t_u_r_e_s _a_n_d _C_h_a_n_g_e_s This section discusses new and changed hardcopy documentation, online information, and ULTRIX Online Documentation (OLD) CD-ROM information. _5._1._1 _H_a_r_d_c_o_p_y _D_o_c_u_m_e_n_t_a_t_i_o_n The following hardcopy documentation has changed: +o The _R_e_l_e_a_s_e _N_o_t_e_s have been revised to contain notes about Version 4.5 of ULTRIX and UWS. +o The _U_L_T_R_I_X _a_n_d _U_W_S _S_y_s_t_e_m _N_o_t_e_s was added to the documentation set in Version 4.3A. This manual contains software and documentation notes from Version 4.4 and earlier _R_e_l_e_a_s_e _N_o_t_e_s that are still relevant to current releases. _N_o_t_e The printed reference pages have not been revised since Version 4.0 of ULTRIX and UWS. Thus, no new reference pages or corrections to existing reference pages have been made to the printed manuals. However, the online reference pages have been maintained. We strongly recommend you use the online reference pages for reference, either by using the _m_a_n command or by using Bookreader (if you have a UWS license). _5._1._2 _U_L_T_R_I_X _O_n_l_i_n_e _R_e_f_e_r_e_n_c_e _P_a_g_e_s The following list contains new and changed online reference pages: accept(2) addnode(8) ar(1)RISC at(1) chpt(8) cp(1) cut(1) dd(1) getsysinfo(2) getutent(3) grep(1) init(8)VAX malloc(3)RISC printcap(5) pstat(8) ranlib(1)RISC sendmail(8) sh(1) sigsetjmp(3) stat(2) tar(1) _5._1._3 _U_W_S _O_n_l_i_n_e _R_e_f_e_r_e_n_c_e _P_a_g_e_s The following list contains new and changed online 5-2 Documentation reference pages: dxmail(1X) Xtx_R4(8X) Xws_R4(8X) Xwst3d(8X) Xqvsm(8x) _5._1._4 _U_L_T_R_I_X _O_n_l_i_n_e _D_o_c_u_m_e_n_t_a_t_i_o_n _C_D-_R_O_M _N_o_t_e_s The order numbers for obtaining ULTRIX Online Documentation (OLD) CD-ROMs are: +o QA-GEW8A-H8: Use this order number to obtain the most recent ULTRIX OLD CD-ROM. +o QT-GEW8A-C8: Use this order number to obtain a bimonthly subscription to the ULTRIX OLD CD-ROM. _5._2 _D_o_c_u_m_e_n_t_a_t_i_o_n _N_o_t_e_s There are no new documentation issues. Refer to the _S_y_s_t_e_m _N_o_t_e_s manual for information about current documentation issues and features not documented elsewhere. Documentation 5-3 Problems Resolved in Version 4.5 A This appendix discusses ULTRIX and UWS customer- reported software problems that have been resolved in Version 4.5. Tables A-1 through A-4 list ULTRIX problems resolved; Table A-5 lists UWS problems resolved. The tables display the topic or the name of the component, a description of the problem, and, when applicable, a reference to the identification code for the problem. Table A-1: _U_L_T_R_I_X _P_r_o_b_l_e_m_s _R_e_s_o_l_v_e_d _i_n _V_e_r_s_i_o_n _4._5 (_A-_F) Component Problem Resolved Problem ID __________________________________________________________ accept(2) The _a_c_c_e_p_t system call QAR 12554 terminated upon receipt of a SIGALRM. Now, it restarts if the signal is received while it is blocked. ar(1)RISC The _a_r -_z command (repress QAR 13302, building of symbol table) QAR 13639, failed. This problem has QAR 13386 been corrected and three previously undocumented options, -s, -h, and -z, have been added to _a_r(1.) arp(8c) A previous change to the QAR 13582, _a_r_p command restricted its QAR 13563 use to the superuser. This fix was too extreme, preventing all users from using, for example, the _a_r_p -_a command. automount(8nfs)The _a_u_t_o_m_o_u_n_t utility did SPR HPAQ13090 not unmount file systems that were mounted with a relative pathname. Table A-1: (continued) Component Problem Resolved Problem ID __________________________________________________________ bindsetup(8) The _b_i_n_d_s_e_t_u_p command used CLD HPAQC3C83 an obsolete template for the _n_a_m_e_d._c_a file. Because the list of root name servers in _n_a_m_e_d._c_a was out of date, customers who wanted to go outside their own zones had to get the current list of root name servers from _n_i_c._d_d_n._m_i_l, and edit the _n_a_m_e_d._c_a file to add them. Running _b_i_n_d_s_e_t_u_p overwrote their _n_a_m_e_d._c_a file and they had to fix it again. binmail(1) Two security-related SSRT394-U- problems have been 282, resolved. SSRT494-U-287 If the timestamp string in SPR HPXQA1766 a received mail message was missing the seconds field, /_u_s_r/_u_c_b/_m_a_i_l did not properly parse the mail file. The _b_i_n_m_a_i_l utility caused CLD HPAQA8F1B the _c_o_m_s_a_t server to occasionally provide empty mail message excerpts when reporting incoming mail. cam A problem which caused the SPR UVO101041 _e_l_c_s_d daemon to hang, thus preventing any further _s_c_s_i/_c_a_m error logging, has been corrected. SCSI bus resets on a DS5100 QAR 13751 resulted in a hung system. A-2 Problems Resolved in Version 4.5 Table A-1: (continued) Component Problem Resolved Problem ID __________________________________________________________ cc(1) RISC only. C programs that CLD HPAQA2AE2 were compiled using the -S option could fail with an out of range message similar to the following: _u_g_e_n:_l_i_b_m_l_d: _I_n_t_e_r_n_a_l: _s_t__p_d_n__i_d_n: _i_d_n (_x_x_x_x_x_x_x_x) _l_e_s_s _t_h_a_n _0 _o_r _g_r_e_a_t_e_r _t_h_a_n _m_a_x (_1_5_4_7_9) The value for _x_x_x_x_x_x_x_x was always a very large number. RISC only. The compiler SPR HPXQ454B2 allowed C++ style comments in a C program, thereby producing failures when compiling with the -_P option. The compiler front end has been modified to not allow C++ style comments in a C program. RISC only. The attempt to QAR 13842 compile a C program that contained any redefinitions of old style formal parameters resulted in a hang. The compiler front end now reports and handles any redefinitions of formal parameters. RISC only. Some sizeof QAR 12630 references that formerly compiled did not compile under the Version 4.5 compiler. RISC only. If a syntax SPR GOZ10044 error occurred in the variable declaration section of the code before function definitions, the compiler produced an incorrect line number for the location of the syntax error. Problems Resolved in Version 4.5 A-3 Table A-1: (continued) Component Problem Resolved Problem ID __________________________________________________________ RISC only. The compiler SPR HPXQ31D40 dumped core with an assertion failed message when an unindexed array was used to reference a structure. RISC only. The compiler SPR ICAX48727 aborted the compilation of a C program that contained very long if-else selection statements with the _y_a_c_c stack overflowed error. The old version of the compiler, which is invoked by using the -_o_l_d_c option, successfully compiled the same program. Attempting to compile a C SPR HPXQ3890F program with option -O or -O2 caused the system to crash with a segmentation fault as the program was being optimized. Compiling the same program without using either option succeeded without errors. Compiling a C program that QAR 13675 contained a #_d_e_f_i_n_e directive with a long token-string (the body of the macro), produced a segmentation fault and caused the system to crash. Typically, the token string in these cases was greater than 4,000 bytes. The C compiler front end, _c_f_e, has been changed to solve this problem. comsat(8c) A security related problem SSRT294-U-272 has been resolved. The _c_o_m_s_a_t command did not CLD UMG00433 notify users with 8- character login ids of incoming mail. A-4 Problems Resolved in Version 4.5 Table A-1: (continued) Component Problem Resolved Problem ID __________________________________________________________ csh(1) The _c_s_h built-in command SPR HPXQ44EAF _n_o_h_u_p did not work. A script that used _n_o_h_u_p to ignore the SIGHUP signal was killed when the SIGHUP signal was sent to it. Now, a script that uses _n_o_h_u_p actually ignores the SIGHUP signal. A _c_s_h memory leak has been CLD EVT100800 corrected. A problem that caused the QAR 13890 _c_s_h shell's internal representation of its path variable to become corrupted has been corrected. crash(8) The _c_r_a_s_h utility has been SPR VN0100008 modfied to correctly display the tty struct of a LAT process. Previous versions of the utility dumped core when attempting to display a LAT tty. ctrace(1) The _c_t_r_a_c_e utility caused QAR 12529, some programs produced by QAR 13336 compiling ctrace output to dump core when executed. cxref(1) The _c_x_r_e_f utility was QAR 13045 unable to handle ANSI prototype declarations. Problems Resolved in Version 4.5 A-5 Table A-1: (continued) Component Problem Resolved Problem ID __________________________________________________________ dbx(1) The _d_b_x utility failed with QAR 13732 a register dump when printing the parameters of a Fortran routine performing the _w_h_e_r_e (stack backtrace) command. Fortran character parameters have a hidden parameter at the end of the parameter list in the symbol table which cannot be printed. The _d_b_x utility now interprets the hidden parameter as the end of the parameter list for the given procedure. The _d_b_x utility set SPR HPAQ82698 breakpoints incorrectly when encountering Fortran _i_f statements. The _d_b_x utility could not CLD MGO100442 always print Fortran n dimensional arrays. A problem related to the CLD HPXQ72E39 _d_b_x utility's ability to set break points and step through Fortran programs that contain alternate entries has been resolved. RISC only. the _d_b_x utility QAR 13846 produced _k_e_r_n_e_l _a_d_d_r_e_s_s (_0_x_f_f_f_f_e_0_1_0) _n_o_t _m_a_p_p_e_d messages when issuing the following command: _p $_c_a_s_e_s_e_n_s_e. The _d_b_x utility was unable SPR UVO100490 to step through or set break points properly in Fortran programs containing the _f_o_r_m_a_t statement. A-6 Problems Resolved in Version 4.5 Table A-1: (continued) Component Problem Resolved Problem ID __________________________________________________________ The _d_b_x utility dumped core QAR 05217 when run on a stripped executable such as /_b_i_n/_u_m_o_u_n_t. The _d_b_x utility no longer dumps core when run on stripped executables. decuniversal_ The _l_g_0_2_o_f and _l_g_3_1_o_f print of filters now determine if a form feed needs to be sent before the reset command to eject any remaining data. With _l_n_0_3_o_f, _l_a_7_5_o_f, SPR _l_g_0_2_o_f, and _l_g_3_1_o_f print SOO100051, filters, you can now print CLD UVO100561 up to 70 lines of text on A4 paper in portrait mode and more than 66 lines of text in landscape mode. You can set up the the filter for A4 paper to specify the page length in the _p_r_i_n_t_c_a_p file, for example: :_i_f=/_u_s_r/_l_i_b/_l_p_d_f_i_l_t_e_r_s/_l_n_0_3_o_f +_z_7_0: The +_z option specifies the real page length in lines. The _p_r_i_n_t_c_a_p _p_l option limits the number lines to print per page. If you want to print 70 lines on 70 line (A4) paper then set both the +_z and _p_l values to 70. dms(8) DMS clients with small QAR 12384 amounts of memory paniced with an _I/_O _e_r_r_o_r _i_n _s_w_a_p error just after completion of their system configuration. dump(8) Several _d_u_m_p command QAR 13650 problems have been resolved. Problems Resolved in Version 4.5 A-7 Table A-1: (continued) Component Problem Resolved Problem ID __________________________________________________________ The QIC tape running at SPR HPXQB43A5 16000 BPI defaulted to 320MB even if the length of the tape was specified in the _d_u_m_p command. egrep(1) The _e_g_r_e_p command dumped SPR UVO100863 core when asked to search for a long expression. elcsd(8) The _e_l_s_c_d daemon sometimes QAR 2149 failed without an error indication when it was unable to locate an entry for _e_l_c_s_d/_u_d_p in the services data base. Now, the _e_l_s_c_d daemon attempts to use a default port number (704) and logs all ALERT errors to /_d_e_v/_c_o_n_s_o_l_e as well as to _s_y_s_l_o_g. enroll(1) RISC only. The _e_n_r_o_l_l CLD HPXQ56F25 command created a key file with all zeros regardless of the specified key, causing secret mail functionality to fail. The problem was caused by a library header file which assumed RISC machines were big-endian. The header file, /_u_s_r/_i_n_c_l_u_d_e/_m_p._h, now implements the "half" structure in a little- endian way for RISC machines. find(1) The -_d_e_p_t_h option of the SPR HPAQ28C24 _f_i_n_d command failed when the -_n_a_m_e file name option was one of the predicates in the expression being tested. A-8 Problems Resolved in Version 4.5 Table A-1: (continued) Component Problem Resolved Problem ID __________________________________________________________ fpc(3) RISC only. Signal handlers QAR 13312 for floating point exceptions (SIGFPE) did not receive adequate exception status to describe the exception condition. The structure was there, but the data was cleared. Valid exception data is now being passed to the signal handler. fseek(3s) Executing the _f_s_e_e_k CLD subroutine from the HPAQ64A29, beginning of a file with an CLD MGO100696 odd offset caused subsequent output to the file to be written to the wrong place on the file. The _f_s_e_e_k subroutine has been fixed to solve this problem. fta(4) The _f_t_a driver could cause QAR 13660 a system to hang if: 1) the system was built with DEFTA support, 2) the device was not enabled by _i_f_c_o_n_f_i_g, and 3) lat was turned on. Additionally, the driver has been modified to more completely report the DEFTA module type. Problems Resolved in Version 4.5 A-9 Table A-1: (continued) Component Problem Resolved Problem ID __________________________________________________________ The FDDI connection on a CLD DECstation configured with HPXQA6B9C, the DEFTA FDDI adapter and CLD HPXLC22D3 the R4000 CPU could be lost after the system reported many apparent FDDI hardware errors. The system reported that the adapter was shut down and went off-line. However, this report occurred when there were no real FDDI errors. The DEFTA device driver has been modified to resolve this problem. ftp(1c) The _f_t_p program ignored directory information in a wildcard copy using the _m_g_e_t command. As a result, errors were produced for files copied to any nonexistent local directories. fza(4) A process hung in D state CLD MGO100242 when accessing remote files in a network file system through the FDDI network. This usually occurred after the network recovered from a previous traffic disruption. The device driver for DEFZA FDDI controller 700/700C has been fixed to solve this problem. A-10 Problems Resolved in Version 4.5 Table A-1: (continued) Component Problem Resolved Problem ID __________________________________________________________ A system with the DEFZA CLD WEASB5886 FDDI controller 700/700C could hang when the system was heavily loaded with FDDI network traffic: _m_b_u_f consumption suddenly and substantially increased, and continued to do so. Eventually, the system became unusable. This problem occurred when user datagrams were not transmitted by the FDDI adapter and were stuck in the FDDI network interface output queue. __________________________________________________________ Problems Resolved in Version 4.5 A-11 Table A-2: _U_L_T_R_I_X _P_r_o_b_l_e_m_s _R_e_s_o_l_v_e_d _i_n _V_e_r_s_i_o_n _4._5 (_G-_M) Component Problem Resolved Problem ID ______________________________________________________ getcwd(3) Programs that used the QAR 13749 _g_e_t_c_w_d routine took too much time to complete when automounted file systems had symbolic links from the root directory to each mount point. Sometimes, the target of this link did not respond quickly (or at all) to _s_t_a_t system calls, because the algorithm used in the _g_e_t_c_w_d routine may have had to _s_t_a_t many (or all) of the entries in the root directory, and perhaps wait for slow _m_o_u_n_t_d servers (or time out on dead NFS servers). Further, the _g_e_t_c_w_d routine hung if the server of any mount point was down. gethostent(3n)The global variable CLD UMG00384, _s_v_c__l_a_s_t_l_o_o_k_u_p did not CLD address the proper HPXQ56FA9, _s_v_c__l_a_s_t_l_o_o_k_u_p value. A newCLD HPAQ651EA __s_v_c__l_a_s_t_l_o_o_k_u_p[] array variable was added to solve this problem. **getpwent(3) The _s_e_t_p_w_e_n_t routine causedSPR ICAX48870 a password file locking problem when aborting from the _p_a_s_s_w_d command. getservent(3n)A memory leak occurred whenQAR IS0100028 the _g_e_t_s_e_r_v_b_y_p_o_r_t was called. A change to the _g_e_t_s_e_r_v_e_n_t code corrected this problem. A-12 Problems Resolved in Version 4.5 Table A-2: (continued) Component Problem Resolved Problem ID ______________________________________________________ getwd(2) The _g_e_t_w_d system call no QAR 13749 longer returns an error when a dangling link from the automount trigger point is encountered during a search back up the tree. Previously, the call returned the message: _p_w_d: _g_e_t_w_d: _N_o _s_u_c_h _f_i_l_e _o_r _d_i_r_e_c_t_o_r_y. Now, the _d_d._s_t__d_e_v variable is set to zero when the _g_e_t_m_n_t routine returns -1, allowing the _p_w_d command to continue (and to return the correct results). hosts(5) The _m_a_k_e__h_o_s_t_s script QAR 13078 created invalid CNAME resource records when the host name in the hosts file contained uppercase characters. ifconfig(8c) The _i_f_c_o_n_f_i_g utility QAR 13702 incorrectly reported the IFF_OACTIVE bit as IFF_PFCOPYALL, and did not report the state of IFF_PFCOPYALL or IFF_802HDR. inet(3n) A root application QAR 13845 attempting raw socket I/O could cause the system to issue the _m__c_o_p_y_3 panic message. inetd(8c) The _i_n_e_t_d daemon did not SPR HPAQ31BF2 restart running processes that were marked wait in its configuration file if it received a HUP signal. Problems Resolved in Version 4.5 A-13 Table A-2: (continued) Component Problem Resolved Problem ID ______________________________________________________ kinit(8krb) A bug in the _l_i_b_c_k_r_b._a SPR 78VB90099 library caused the _n_a_m_e_d daemon to run out of file table entries. The problem was caused by a library routine which did not close the /_e_t_c/_r_e_s_o_l_v._c_o_n_f file in an error situation. The _n_a_m_e_d daemon eventually issued the following message: _n_a_m_e_d: _a_c_c_e_p_t: _T_o_o _m_a_n_y _o_p_e_n _f_i_l_e_s. ksh(1) The Korn shell built-in SPR _g_e_t_o_p_t_s option has been MGO100027, fixed to work as documentedSPR MGO100028 in the reference pages. Additionally, the _i_f command now handles multiple expressions. The _k_s_h shell could hang QAR 13853 the system when it attempted to execute _k_s_h scripts. If a _k_s_h script that had SPR HPAQ68A7E the same name as another executable already in the user's path was invoked by specifying its full pathname and the script was in or below the user's current directory, the _k_s_h shell executed the file it found in its path search rather than the script. The _k_s_h shell prevented QAR 13862 normal I/O redirection to special files ( /_d_e_v/_n_u_l_l in particular) when the _n_o_c_l_o_b_b_e_r option name was used. A-14 Problems Resolved in Version 4.5 Table A-2: (continued) Component Problem Resolved Problem ID ______________________________________________________ An invalid pointer to the CLD ZUO100153 next argument caused some scripts to fail with segmentation faults and bus errors. Executing two _s_u commands SPR ICAX44686 in a _c_s_h script to a _k_s_h user stopped the output from the second _s_u process. The Korn shell did not handle the SIGTTOU signal properly. ld(1) The _l_d command could dump CLD HGOQ90038 core with the following message: _F_a_t_a_l _E_r_r_o_r _i_n: /_u_s_r/_l_i_b/_c_m_p_l_r_s/_c_x_x/_l_d - _c_o_r_e _d_u_m_p_e_d. lockd(8c) A condition which could CLD cause the _l_o_c_k_d daemon to HPXQ38419, go into an infinite loop CLD KAOQ41533 has been eliminated. login(1) The _l_o_g_i_n utility has been QAR 13709 fixed to correctly log the user name in the /_v_a_r/_s_p_o_o_l/_m_q_u_e_u_e/_s_y_s_l_o_g file after repeated login failure attempts. Problems Resolved in Version 4.5 A-15 Table A-2: (continued) Component Problem Resolved Problem ID ______________________________________________________ lprm(1) The _l_p_r_m command could not SPR UVO101898 remove print jobs from a queue when a system had more than one network interface and the following conditions applied: One interface was configured with the hostname of the system and the other interface was configured with a different name, and the print jobs were submitted using the _l_p_r command through the interface that was not configured with the hostname of the server. Attempts to remove such a request failed with a permission denied message. lprsetup(8) A security-related problem SPR T394-U- has been resolved. 275 lseek(2) The _l_p_d line printer daemonCLD9 WFBB3708 caused the print filter to corrupt the printer output by making the filter reread a block of the input file. The cause of this problem was _l_s_e_e_k, which the daemon called: _l_s_e_e_k was not operating atomically. lta(5) The _l_t_a_r_e_s_e_t routine CLD UVO101401 received a kernel segmentation violation panic that was caused by a terminal server sending a server portname longer than 16 bytes to the _l_a_t server. mail(1) The /_u_s_r/_b_i_n/_m_a_i_l utility CLD EVT100615 created /_t_m_p/_m_a_a* files with improper ownership when the /_u_s_r/_s_p_o_o_l/_m_a_i_l file system was full. A-16 Problems Resolved in Version 4.5 Table A-2: (continued) Component Problem Resolved Problem ID ______________________________________________________ The /_u_s_r/_u_c_b/_M_a_i_l and QAR 13700 /_u_s_r/_u_c_b/_m_a_i_l utilities processed mail escape sequences when the mail session was not interactive. make(1) Applications that used QAR 13651 enumerated constants in arithmetic expressions dumped core with segmentation violation error messages. msgrcv(2) Systems configured with QAR 13293 MSGMAX and MSGMNB values of 32768 or more panicked with the message _b_a_d _r_m_f_r_e_e when an attempt was made to receive a message of size 32768 or more. The _m_s_g_r_c_v system call now properly receives the message. ______________________________________________________ Problems Resolved in Version 4.5 A-17 Table A-3: _U_L_T_R_I_X _P_r_o_b_l_e_m_s _R_e_s_o_l_v_e_d _i_n _V_e_r_s_i_o_n _4._5 (_N-_R) ________________________________________________________ Component Problem Resolved Problem ID ________________________________________________________ nawk(1) The _n_a_w_k command, _g_e_t_l_i_n_e, QAR 13281 when reading from a named pipe, sometimes hung because the buffered output was not flushed after all the writes were performed. A local variable in the QAR 13864 function line list (but not a formal parameter) used as an array did not get cleared the second time the function was called. nfs(5nfs) The client crashed when theCLD 9WFBB1863 application that had the sticky bit set on the server was executed. The server/client set attributes routines have been modified to fix the problem. When a user tried to modifyCLD HPAOB35A9 a file on an NFS-mounted filesystem with quotas enabled, and that user's quota was then exceeded, the file was deleted and no errors were reported to the user. An NFS server could crash CLD EVT100737 with the panic message _s_m_p__l_o_c_k__l_o_n_g: _b_e_y_o_n_d _s_l_e_e_p _c_o_u_n_t when a file on it was being accessed by an NFS client. A-18 Problems Resolved in Version 4.5 Table A-3: (continued) ________________________________________________________ Component Problem Resolved Problem ID ________________________________________________________ An NFS server could panic CLD EVT100672 when one client removed the files that another client was writing to. The server then panicked with either of the following messages: _g_n_o_d_e _i_s _i_n_a_c_t_i_v_e or _g_f_s__l_o_c_k:_l_o_c_k_i_n_g _u_n_r_e_f_e_d _g_n_o_d_e. File copies on NFS mount CLD HPAQ86D35 points did not work correctly if full path names were specified. Kernels panicked if entriesCLD ZPOQ40019 at the end of directory blocks were too short to be valid entries. The _n_f_s__p_u_t_r_d_d_i_r_r_e_s routine was modified to print a _b_a_d _d_i_r_e_c_t_o_r_y error message if this happens. An SMP machine with CLD HPXL35428 multiple CPUs heavily utilized as an NFS file server crashed with the _s_m_p__l_o_c_k__l_o_n_g: _l_o_c_k _p_o_s_i_t_i_o_n _m_e_s_s_u_p and _s_e_g_m_e_n_t_a_t_i_o_n _f_a_u_l_t panic messages. The system usually had many nfsd daemons running. nslookup(1) The _n_s_l_o_o_k_u_p command did SPR UVO101899 not return the name of a site when it was looked up by address. The _n_s_l_o_o_k_u_p command dumpedSPR UTO100334 core when run using an IBM/AIX version 3.25 system as a name server. Problems Resolved in Version 4.5 A-19 Table A-3: (continued) ________________________________________________________ Component Problem Resolved Problem ID ________________________________________________________ pack(1) The _p_c_a_t command did not SPR ICAX46672 handle wildcards. This problem has been fixed by correcting the _u_n_p_a_c_k module to handle the _p_c_a_t command properly. pixie(1) The _p_i_x_i_e program dumped SPR HPXQB1216 core when it was run on a stripped executable. pstat(8) The _p_s_t_a_t -_s command now QAR 13836 displays the available swap space in units of 32KB and 1KB buffers. Additionally, the time it takes for the display to return has been improved. rdump(8c) The _r_d_u_m_p command dumped QAR 13576 core when the /_e_t_c/_d_u_m_p_d_a_t_e_s file was missing. Several _r_d_u_m_p command QAR 13650 problems have been resolved. recv(2) The _r_e_c_v system call alwaysQAR 12554 terminated upon receipt of a SIGALRM. Now, it restarts if the signal is received while it is blocked. restore(8) The _r_e_s_t_o_r_e command exited,CLD HHPAQC5600 reporting a failure to open the /_d_e_v/_t_t_y file when it was used with the _r_s_h command. Now, when the same failure occurs, the command issues the message _O_p_e_n_i_n_g /_d_e_v/_n_u_l_l _i_n_s_t_e_a_d. _N_o _i_n_t_e_r_a_c_t_i_v_e _r_e_s_t_o_r_a_t_i_o_n _i_s _p_o_s_s_i_b_l_e. A-20 Problems Resolved in Version 4.5 Table A-3: (continued) ________________________________________________________ Component Problem Resolved Problem ID ________________________________________________________ These _r_e_s_t_o_r_e and _r_r_e_s_t_o_r_e OSF CLD 7HRBB1511 command problems have been resolved: 1) The maximum blocking factor that the _r_r_e_s_t_o_r_e command could handle was restricted to the maximum size of a socket. This restriction has been eliminated. 2) A segmentation fault that could occur when using the _b option has been eliminated. Now, when read errors occur, the correct blocking factor is used. Several _r_e_s_t_o_r_e command QAR 13650 problems have been resolved. rlogin(1c) With a YP distributed ICA 44254, ICA _p_a_s_s_w_d database and 43081, QAR 9861, overrides in the local QAR 10456 /_e_t_c/_p_a_s_s_w_d file, an _r_l_o_g_i_n command to a system failed with a variety of errors. For example: _L_o_g_i_n _i_n_c_o_r_r_e_c_t; _c_a_n'_t _f_i_n_d _l_o_g_i_n _d_i_r_e_c_t_o_r_y and _i_n_v_a_l_i_d _s_h_e_l_l. A _r_l_o_g_i_n command failed QAR 10456 because the local password file contained an entry overriding some yp password file fields and the user had a ._r_h_o_s_t_s file that normally allowed him to log in to the system without specifying a password. rmt(8c) The _r_m_t command hung if QAR 13650 requested to process a 64KB read. rrestore(8c)Several _r_r_e_s_t_o_r_e command QAR 13650 problems have been resolved. Problems Resolved in Version 4.5 A-21 Table A-3: (continued) ________________________________________________________ Component Problem Resolved Problem ID ________________________________________________________ rshd(8c) The _r_s_h_d command caused CLD HPAQ66C46, control not to be returned CLD 774SA3852 to the user's terminal until all processes started on the remote system. ________________________________________________________ A-22 Problems Resolved in Version 4.5 Table A-4: _U_L_T_R_I_X _P_r_o_b_l_e_m_s _R_e_s_o_l_v_e_d _i_n _V_e_r_s_i_o_n _4._5 (_S-_Z) Component Problem Resolved Problem ID _____________________________________________________ s5make(1) The _s_5_m_a_k_e command produced SPR HPXQ85B25 segmentation faults when making files that required multilevel macro translations. sed(1) The _s_e_d command dumped core SPR TKTR81132 when performing a substitution on an input line of 4096 characters or more. sendmail(8)VAX only. The _s_e_n_d_m_a_i_l CLD HPALAAA94 program sometimes dumped core on VAX systems. A boolean option, _G, has SPR ICAX46310 been added to the _s_e_n_d_m_a_i_l command. This option turns on and off the fuzzy feature. By default, the _G option is true. To turn it off, either set on the command line using -o flag or set it in the configuration file. For more information, see _s_e_n_d_m_a_i_l(8). Security-related problems CLD UMG00512, have been resolved. CLD UMG00567 setjmp(3) RISC only. The _s_e_t_j_m_p() QAR 13841 and _s_i_g_s_e_t_j_m_p() routines allowed a process to be killed with a _s_e_n_d_s_i_g: _c_a_n'_t _g_r_o_w _s_t_a_c_k message. sh(1) An interactive _s_h script SPR HPXQ107AE did not exit when issuing the exit command. The _s_h shell did not return SPR HPAQC3D68 0 when an if statement was executed and no then or else list was executed. Problems Resolved in Version 4.5 A-23 Table A-4: (continued) Component Problem Resolved Problem ID _____________________________________________________ The _s_h shell caused QAR 1322l temporary files to remain after issuing an _e_x_e_c command rather than deleting them. sh5(1) Executing two _s_u commands CLD STLQB1290 in a _s_h_5 script to a _k_s_h user stopped the input/output from the second su process. snmpd(8n) The _s_n_m_p_d daemon issued a CLD E20BA0995 success return if it received a request to change the status of a network interface. In reality, no actual change to the hardware interface occurred. The _s_e_t interface routine has now returns an error instead of a success for this requested function. Under severe stress CLD E32BA92404 conditions, many occurances of the message: _S_N_M_P_D: _S_N_M_P_I_N: _e_r_r_o_r _i_n _P_R_O_C__S_N_M_P__M_S_G, _C_O_D_E -_4 appeared in the error log. Eventually all the available system resources were consumed. sys The wasted swap space CLD CXO-10708, numbers for the _p_s_t_a_t CLD WEAS- command were incorrect. 91714, CLD 9WFBA5745 Now, a child process of a CLD HPAQC9495 SYSTEM_FIVE process no longer inherits the SYSTEM_FIVE signal handling characterics. As a result, System V handling of the SIGCHLD signal does not affect POSIX child processes. A-24 Problems Resolved in Version 4.5 Table A-4: (continued) Component Problem Resolved Problem ID _____________________________________________________ If a process had interval QAR 6622 timers enabled through the _s_e_t_i_t_i_m_e_r routine, they were inherited by any child processes it forked, even though the _e_x_e_c system call had reset all the signal handlers that normally catch them. The state of interval timers is no longer preserved across the _e_x_e_c system call. RISC only. An SMP machine CLD UVO102678 with multiple CPUs could crash with the trap panic when the second CPU was started manually. Output to a console device CLD HPAQC68F4 /_d_e_v/_c_o_n_s_o_l_e, which was first opened in termio raw mode, could be blocked indefinitely if output was stopped by the system when it ran out of buffer space to store characters written to the console. For example, this problem could occur when many user processes wrote to the console. When console output was blocked, any attempt to write to it failed. A command appeared to be hung indefinitely if it had to wait for the write to be completed. LAT buffers were not always CLD EVT100950 freed, eventually causing the kernel to run out of MBUFs. Problems Resolved in Version 4.5 A-25 Table A-4: (continued) Component Problem Resolved Problem ID _____________________________________________________ Segmentation violations occurred while running executables that contained a static const declaration followed by a static variable that was initialized within the declaration. BSD executables were being CLD UVO100771 run with a non-BSD compatibility mode when non-BSD processes issued an _e_x_e_c system call. If a process waiting to CLD UVO100699 open a file that was already opened by another process with mode O_BLKANDSET was killed before the open completed, the system panicked with a segmentation violation. Multiple processes having CLD HPAQ52EOE the same parent sometimes hung if they tried to lock the same file. A change to the _f_c_n_t_l code in the kernel has resolved this problem. A-26 Problems Resolved in Version 4.5 Table A-4: (continued) Component Problem Resolved Problem ID _____________________________________________________ RISC only. RISC systems CLD 9WFBC5758, did not use kernel memory CLD 7BXB35390 efficiently when most kernel memory allocation requests were for memory fragments of small size. Systems with a small amount of physical memory ran out of kernel memory when the latter was in great demand. A new option to the _p_a_r_a_m._c file has been added to allow more efficient use of kernel memory for such systems. To choose the option, set the _g_u_a_r_d_p_a_g_e_s variable in the _p_a_r_a_m._c file to be zero. The default value of _g_u_a_r_d_p_a_g_e_s is GUARDPAGES. RISC only. The expanded CLD GOZ10080 data segment of RISC could overlap a shared memory segment beneath it in the user address space. The shared memory system has been fixed to correct this problem. An option to the _p_a_r_a_m._c CLD GOZ10080 file has been added. The option is _u_s_r_s_m_s, a configurable parameter which is the address that defines the lower boundary of the shared memory segments allocated above the stack segment. See Section 3.3.1 for more information. Problems Resolved in Version 4.5 A-27 Table A-4: (continued) Component Problem Resolved Problem ID _____________________________________________________ An SMP system with TCP CLD UVO100512, loopback enabled could CLD UVO1905 panic with the message _m__f_r_e_e _h_a_s _b_a_d _m__c_l_t_y_p_e when a CPU attempted to close a TCP connection which was already closed by another CPU. The CPU panicked because it accessed the deallocated memory of the connection. SoftPC users were not QAR 13070 allowed to eject the CD by pushing the eject button on the CD-ROM drive, or by using program-eject code after SoftPC had accessed the CD-ROM. As a result, SoftPC programs that used more than one CD could not run. The _p_t_y ports were getting CLD KAOQC1010 hung and they could not be closed or reused until the system was rebooted. The TS_ISOPEN flag was cleared in the _p_t_y_c_c_l_o_s_e subroutine to solve this problem. Occasionally, _m__c_o_p_y_3 CLD MGO100219, panics occurred on a page CLD E20BB0796, fault. Processes, when CLD WEASB2930, halted, occasionally CLD MGO100331, restarted with sockets CLD MGO100332, pointing to _m_b_u_f_s that were CLD UVO100741 freed by other processes. The _f_a_s_t_t_c_p__s_o_s_e_n_d kernel routine was fixed to solve this problem. A-28 Problems Resolved in Version 4.5 Table A-4: (continued) Component Problem Resolved Problem ID _____________________________________________________ A process using the _v_m_s_t_a_t CLD HPAQ7541E -_K command to read the dynamic portion of KSEG2 (through /_d_e_v/_k_m_e_m ) could cause a system panic with either the _s_m_p__l_o_c_k__l_o_n_g: _l_o_c_k _p_o_s_i_t_i_o_n or the _t_l_b_m_i_s_s _o_n _i_n_v_a_l_i_d _k_e_r_n_e_l _p_a_g_e message. The problem was caused by a lack of protection of the PTE for the specified page. The PTE is now properly protected in the /_d_e_v/_k_m_e_m driver. stdio The _t_m_p_n_a_m routine of SPR TKTBB5043 _l_i_b_c._a has been fixed to prevent the corruption of substrings used in strings that contain the temporary file names. swapon(2) The _s_w_a_p_o_n system call QAR 13872 returned ENODEV if the device being configured was not configured into the kernel as a potential swap device. The system call now returns EINVAL in this situation. tar(1) The _t_a_r command failed QAR 13784 while issuing reports such as _T_H_I_S _I_S _A _D_I_R_E_C_T_O_R_Y (the result of a perror with errno 2), and neither the directory nor the file were extracted. Now, the missing directory (and subsequently the file) is extracted. The _t_a_r command hung SPR UVO102580 whenever extracting a file from a tape where the second file on the tape had a blocksize of zero. Problems Resolved in Version 4.5 A-29 Table A-4: (continued) Component Problem Resolved Problem ID _____________________________________________________ telnet(1c) The maximum segment size of CLD MGO100633 a TCP packet was set to zero when a PC running KEALNK PC/TCP established a telnet connection, resulting in a kernel trap. The _t_c_p__i_n_p_u_t module was modified to fix the problem. A _t_e_l_n_e_t command to a local CLD HPAQ81F4B host with a specified port number resulted in a delay prior to the login prompt because the connection ran out of stack frames before completing the loopback negotiations. The number of stack frames has been increased to prevent this from happening. termcap(3x)The _t_n_c_h_k_t_c routine in SPR HPXQB87FD /_u_s_r/_l_i_b/_l_i_b_t_e_r_m_l_i_b._a has been fixed to correctly check the null string termination of the TERM environment variable. test(1) The _t_e_s_t -_w command in a SPR HGOQ10130 shell script with set group id bit set did not function correctly. The _t_e_s_t command only used the real gid and the real uid, instead of the effective gid and uid. tty(4) The _t_t_y driver allowed a QAR 8387, SPR user to exhaust the _c_l_i_s_t GOZ100050 buffers, thereby making the system appear to be hung. uerf(8) The _l_p_s_c_o_m_m routine caused QAR 13831 a number of _u_n_a_l_i_g_n_e_d _d_a_t_a _a_c_c_e_s_s messages to be sent to the system error log. A-30 Problems Resolved in Version 4.5 Table A-4: (continued) Component Problem Resolved Problem ID _____________________________________________________ vi(1) The temporary file created CLD WEABC1258 by the _v_i editor was named in the format of ExPID. Now, the format is changed to Ex[a-z]PID. The change has been made to prevent the failure of the _v_i -_r command on heavily loaded systems. ypserv(8yp)A security-related problem CLD UVO101416 has been solved. The _y_p_s_e_r_v and _p_o_r_t_m_a_p SPR HPAQ2CA38 daemons did not support subnet validation of client requests. Now, they do, using the /_e_t_c/_s_e_c_u_r_e_n_e_t_s file. The _y_p_s_e_r_v server did not QAR 13253 always respond to Sun or PC clients. _____________________________________________________ Problems Resolved in Version 4.5 A-31 Table A-5: _U_W_S _P_r_o_b_l_e_m_s _R_e_s_o_l_v_e_d _i_n _V_e_r_s_i_o_n _4._5 _____________________________________________________ Component Problem Resolved Problem ID _____________________________________________________ dxdb(1X) The _d_x_d_b utility caused a SPR HPAQ53161 segmentation fault when the user attempted to open an executable file that was specified as a source file. install The UDWSYSMGNT subsets UWSQAR 5354 previously did not take into account that there are two versions of _d_x_p_r_e_s_t_o, one for the XUI interface and one for the MOTIF interface. Previously, no matter which interface you choose during installation, you obtained the XUI version of _d_x_p_r_e_s_t_o. Now, a new subset, DXMSYSMGNT/DXVSYSMGNT for the MOTIF version has been added and the SYSTEM MANAGEMENT subsets are now split into two subsets, one for the XUI interface and one for the MOTIF interface. Xserver X11R4 only. The X11R4 X CLD UVO101007 server caused the message _f_i_x_e_d _u_p _u_n_a_l_i_g_n_e_d _a_c_c_e_s_s to be sent to the system error logger when the X server was displaying certain fonts. X11R4 only. The X11R4 CLD TKTRA1562 server did not support the CapBut cap-style on PXG graphics cards. X11R4 only. Intermittent CLD server crashes and UVO100349, unaligned data access CLD WEASC5225 errrors occured on the X11R4 server because pcf fonts did not define all font entries. A-32 Problems Resolved in Version 4.5 Table A-5: (continued) _____________________________________________________ Component Problem Resolved Problem ID _____________________________________________________ X11R4 only. The HX CLD UVO10109 graphics option on the X11R4 server failed to draw dotted lines correctly. _____________________________________________________ Problems Resolved in Version 4.5 A-33