Patch Name: PHNE_7514 Patch Description: s700_800 10.X cumulative telnet(1) patch Creation Date: 96/06/10 Post Date: 96/07/14 Hardware Platforms - OS Releases: s700: 10.01 10.10 s800: 10.01 10.10 Products: N/A Filesets: InternetSrvcs.INETSVCS-RUN Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHNE_7514 Symptoms: PHNE_7514: The following symptoms correspond to the descriptions in the defect descriptions field for PHNE_7514: 1. The telnet(1) command does not accept binary mode negotiation initiated by the Telnet server. 2. The telnet(1) command puts out unwanted and unnecessary messages concerning the toggling of local flow control. The messages are: Local flow control on Local flow control off PHNE_6068: The following symptoms correspond to the descriptions in the defect descriptions field for PHNE_6068: 1. The telnet(1) command does not change the ixon, ixoff, and ixany flags on the Telnet client device when a change in flow control is requested by the Telnet server. 2. The telnet(1) command does not print out a message when a change in flow control (as requested by the Telnet server) occurs. PHNE_5945: The following symptoms correspond to the descriptions in the defect descriptions field for PHNE_5945: 1. The telnet(1) command consumes a large percentage of the CPU when: a. Running in the background (using the Bourne shell) b. Having its input redirected from a file (such as /dev/null) c. Having its input supplied via a pipe. Defect Description: PHNE_7514: The following defect descriptions are for PHNE_7514: 1. The problem is that the acceptance of a binary mode negotiation initiated by the Telnet server within the telnet(1) command is simply not implemented. 2. The problem is that the design of the telnet(1) command does not take into account the many ways in which Telnet is used and how each of those ways may be affected by unexpected and unsolicited messages (such as those concerning the toggling of local flow control). NOTE: The local flow control status is now given within the status output of the telnet(1) command. PHNE_6068: The following defect descriptions are for PHNE_6068: 1. The problem is that the setcommandmode() function is not being invoked correctly so as to change the ixon, ixoff, and ixany flags on the Telnet client device. 2. The problem is that the code to print out a message is being invoked any time the Telnet client device mode is changed and should only be invoked when an actual change in flow control occurs. PHNE_5945: The following defect descriptions are for PHNE_5945: 1. The problem is that the telnet(1) command continues to poll its input even if it has reached the end-of-file and is not a tty. This incessant polling causes the CPU consumption. SR: 4701319202 5003315994 4701304550 5003222901 Patch Files: /usr/bin/telnet what(1) Output: /usr/bin/telnet: Copyright (c) 1988 Regents of the University of Cali fornia. main.c 1.10 (Berkeley) 11/18/88 Revision 1.1.111.5 PHNE_7514 Tue Jun 4 16:29:32 GMT 1996 commands.c 1.15 (Berkeley) 2/6/89 network.c 1.13 (Berkeley) 6/29/88 ring.c 1.10 (Berkeley) 6/29/88 sys_bsd.c 1.16 (Berkeley) 11/29/88 telnet.c 5.38 (Berkeley) 2/6/89 terminal.c 1.13 (Berkeley) 6/29/88 tn3270.c 1.16 (Berkeley) 11/30/88 utilities.c 1.11 (Berkeley) 2/6/89 cksum(1) Output: 1943558093 57344 /usr/bin/telnet Patch Conflicts: PHNE_6174 Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_5945 PHNE_6068 Equivalent Patches: PHNE_7110: s700: 9.01 9.03 9.05 9.07 s800: 9.00 9.04 PHNE_7670: s700: 10.00 s800: 10.00 PHNE_7671: s700: 10.20 s800: 10.20 Patch Package Size: 110 Kbytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHNE_7514 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHNE_7514.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHNE_7514.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. The cluster clients must be shut down as described in step 5b. By default swinstall will archive the original software in /var/adm/sw/patch/PHNE_7514. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHNE_7514.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHNE_7514.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None