Patch Name: PHNE_12399 Patch Description: s700 9.0[357] ARPA Transport cumulative patch Creation Date: 97/09/05 Post Date: 97/09/10 Hardware Platforms - OS Releases: s700: 9.03 9.05 9.07 Products: N/A Filesets: BSDIPC-SOCKET KERN-BLD NET NETINET NETIPC Automatic Reboot?: Yes Status: General Release Critical: Yes PHNE_12399: PANIC PHNE_9100: PANIC PHNE_9028: PANIC PHNE_7252: PANIC PHNE_6707: PANIC PHNE_6227: PANIC PHNE_5361: PANIC PHNE_5010: PANIC PHNE_4587: PANIC PHNE_3939: PANIC PHNE_3657: PANIC PHNE_3579: PANIC Path Name: /hp-ux_patches/s700/9.X/PHNE_12399 Symptoms: PHNE_12399: See Defect Description Defect Description: PHNE_12399: ( SR number: 1653163436 ) TCP client is connected to itself hangs the session. 8/25/97 ( SR number: 1653198069 ) System hangs during shutdown in sbdrop. ( SR not found ) IP directed broadcast forwarding is not supported. ( SR number: 4701350173 ) System panic during start-up, due to lack of defensive check in IP interrupt processing. ( SR number: 5003372144 ) A system panic was caused by null pointer derefenence during a bind(2) system call. PHNE_9100: ( SR number: 5003292979 ) The problem is that Unix Domain sockets that pass file access rights to each other can cause system panics with the message "Data page fault". ( SR number: 5003314302 ) System panics updating an arp entry. ( SR number: 5003316810 ) System hang and network congestion. ( SR number: 5003318543 ) Memory leak when IPPROTO_TCP setsockopt() done on closed socket. ( SR not found ) data memory protection fault panic in whohas_snap8025 ( SR number: 5003327973 ) Data was put in the socket buffer before calling tcp to send it out. If tcp gets an error from the interface which may be transient, tcp returns the error to the application. If the application attempts to resend the data instead of exiting, a potential data corruption situation can occur. ( SR number: 5000716316 ) System hung when doing a second connect() on the same socket. ( SR number: 4701335554 ) ( SR number: 4701335596 ) A syn attack can result in Denial Of Service (DOS) to legitimate users. PHNE_9028: ( SR number: 5003342071 ) ping can cause panic. PHNE_7252: ( SR number: 5003101527 ) Panic occurs trying to free freed mbuf: trap type 15, pcsq.pcoq = 0.123f2c, isr.ior = 0.106a @(#)9245XA HP-UX () #1: Mon Mar 18 14:09:46 PST 1991 panic: (display==0xb200, flags==0x0) Data segmentation fault Kernel Stack trace: panic+0x001c trap+0x0a64 $thndlr_rtn+0x0000 m_free+0x001c m_freem+0x0014 sou_clean+0x0030 sou_delete+0x00b4 ipcshutdown+0x02b4 new_ipcshutdown+ syscall+0x0230 ( SR number: 4701218651 ) When an icmp destination unreachable message is received, an error is placed on ALL sockets which are sending to the specified destination ip address, as opposed to the specific connection which caused the icmp message. TCP does not abort the connection in this case (as the submitter suggests), but the application receiving an error on the socket is most likely aborting the connection. ( SR number: 4701197269 ) Customer wants better performance for pure lan topologies, especially with fddi. The current implementation will limit the maximum packet size to 512 bytes of user data when going to a remote network across a gateway. This limitation is is a little too strict for topologies that are made up entirely of fddi and/or ethernet lans. The result is an unnecessary limitation in throughput. Customers installing fddi (for performance benefits) are especially annoyed by this. ( SR not found ) This problem was found by testing ioctl(NMIOGET) for ID_ipAddrTable. When *nmparms.len is given with a fairly large value, system panic. Since ioctl(NMIOGET) is only for internal customer (for developing snmpd), this problem is not expected to happen. ( SR not found ) Two problems may occur when ioctl (command = NMIOGET) is used to retrieve the address translation table (atTable): these problems could either overrun user buffer or return inconsistent information. Since this is for internal use only, customers should not see this. ( SR number: 1653055426 ) One symptom experienced by the customer was the failure of the rpcinfo command: /usr/etc/rpcinfo -u nfs This command will time out if the patches PHNE_2375 and PHNE_2551 have been applied, and if the interface for the local IP address supports checksum offload. This latter condition is satisfied for the loopback interface 127.0.0.1, and for some FDDI interfaces. ( SR not found ) Incorrect NMIOSET(ID_ipRouteEntry) deletes the route entry. Ioctl(NMIOSET) with nmparms.objid equals ID_ipRouteEntry is to set the new gateway for a route entry. Since this is for internal use, customers should not experience this. ( SR number: 1653055103 ) Missing parameter cause system panic. ( SR number: 5000695213 ) The customer would like an enhancement to the arp(1m) command to: - be able to disable unicast arp's - configure the timeout value for arp entries Disabling unicast arp's will result in decreased lan traffic, which can be a significant percentage of overall lan traffic in large networks. Configureable timeouts will have a similar effect, and allow system administrators to more intelligently control network utilization. NOTE: commands are not yet part of general release patch. ( SR number: 5003146415 ) Cust has an application that creates an async socket, and when a client connects to it, it then writes data to it. Eventually the data buffer fills up (as the client doesn't read), and we get an ewouldblock error. This is okay. What's not okay, is that we don't get a SIGIOsignal delivered to us when buffer space becomes available. ( SR number: 4701223040 ) Maximum IP packet size limited to 32 KBytes. ( SR number: 5003166975 ) For releases 9.03 and 9.04, the TCP "keepalive" function no longer works on connections to/from non-hp 9000 systems. This means that customers will notice that connections which are idle, i.e. have no activity, will time out after a period usualy not exceeding one hour. This is most commonly noticed when using vt3k to connect to HP 3000 systems. ( SR number: 4701237263 ) IP cannot reassemble datagrams when the fragment offset is greater than 32KBytes. ( SR number: 1653077800 ) ( SR number: 5003170332 ) When the ipq reassassembly queue is first initialized an assumption is made that if the first fragment was checksum offloaded all successive fragments for the datagram would be checksum offloaded as well. In this case FDDI computed the checksum on the last fragment, based on the data length in the mbuf which included the ethernet padding left attached by the translating bridge. FDDI then compares the data length in the mbuf to the length value in the IP header and seeing that they differ disables the MF_CKO_IN flag and sends the fragment on up. So far this problem only seems to occur when the data is fragmented (as UDP data is), when the route originates on an ethernet host and passes through a translating bridge to an FDDI link, and when the record size is such that the last IP fragment is smaller than the ethernet minimum length which causes padding to be appended to the last fragment. ( SR number: 5003179093 ) Customer has an application that for performance reasons needs to burst UDP packets to the HP in quanties of 32k or more. There could be multiple machines sending the data at the same time to the same socket causing very large (150k or more) socket buffer requirments. The enhancement to allow 500k to 1000k of socket space would solve the customers problem. We have been able to adb the kernal and override the socket size to be 1000k and the problem went away. This would prove some justificaton for the larger socket sizes. A different way to solve this problem may be to find out why we are overflowing when we hit the 1/4 full mark on the socket. ( SR number: 4701253880 ) If two address belonging to the same system are listed in succession in the IP options array of an incoming datagram, the datagram will be passed up to the upper layer protocol (where it is dropped) rather than being forwarded to the next system in the options array. ( SR number: 1653080929 ) System panic with prb_ntnew top of stack. This occurs when HP 9000 receives a probe unsolicited reply with a corrupted name, i.e. a name with any bytes having the sign bit set. ( SR number: 5003185900 ) When an HP system receives a link layer broadcast for a network it does not belong to it will forward the datagram to it's default gateway. This is in violation of RFC 1009 which states "a gateway must not forward a datagram which arrives via a local network broadcast". ( SR number: 5003171686 ) After doing a vt3k to a non-existant probe will time out and the user will get an ipc error 40. However, the name remains in the cache and the node can't be reached even if it subsequently comes up or its name is added to a proxy server until the cache entry times out and is deleted. ( SR number: 4701253898 ) IP source routing is not be handled correctly by IP. This can be seen by a call to setsockopts and immediately calling getsockopts to retrieve the option array. The information is quite different from what was passed in and as suspected, the routing information in the IP header is incorrect as well. ( SR number: 5003192807 ) ( SR not found ) Xinet's Appletalk product not working in 9.03, 9.04. ( SR not found ) The connecting requests were completed and wait for accept() issued by socket application to pick. But if new connecting reqeusts were keeping established, the accept() will pick the one just completed and the old completed connection just keep staying in the tail of queue and starved for the accept(). ( SR number: 4701249946 ) When ip_forward can't forward a packet it does not increment the ips_cantforward counter. Secondly, it is incorrectly incrementing ipInAddrErrors when time-to-live expires and should instead increment ipInHdrErrors as per RFC 1158. ( SR number: 5003194134 ) After receiving a signal in recv, recvmsg, or recvfrom, when the user specifies SIG_RESTART to restart the system call, socket code will zero out the length field of the returned address. This will cause the system call to not return the returned address. ( SR not found ) As per RFC 1122 ICMP error messages should not be sent for link layer broadcasts. ( SR number: 4701253252 ) With auditing of ipcdgram turned on, system will panic or hang when calling sendto() if the sockaddr_in structure is not word aligned. ( SR number: 5003196360 ) Large UDP datagrams can not be sent through the loopback interface due to udp checksum errors. The errors start occurring at the first datagram to be fragmented by IP. ( SR number: 5000707950 ) panic: mclfree Dump will show a corrupted mbuf being freed. m_len will be negative, m_off will be some positive multiple of 0x28, which is the tcp/ip header size. ( SR number: 5003204222 ) ( SR number: 5003216903 ) System panic in mclfree. ( SR number: 5003228270 ) Routes for up and running SLIP interfaces can get deleted when other SLIP interfaces are started. This will happen only when the interfaces are started in a different order from which they originally were. For instance a system with two SLIP ni's uses the addresses 23.1.1.1 and 24.2.2.2. If ni0 is started with address 23.1.1.1 and ni1 is started with 24.2.2.2. If ni0 is later restarted with the address of 24.2.2.2 then when ni1 is restarted using 23.1.1.1 the route for ni0 (24.2.2.2) will be deleted since that was the old address attached to ni1. ( SR number: 1653109991 ) HP nodes are unable to connect to IBM hosts via SNAP over 802.3 when the HP node initiates the connection. ( SR number: 5003229070 ) Transmitting large files over a local NFS mounted directory results in UDP checksum errors. The NFS mount appears to hang during this time. ( SR number: 5003229229 ) The customer will experience a system hang. On a uniprocessor system, an "ack storm" can be seen using a network analyzer. On an MP system, the storm may be in loopback, so an analyzer will not show anything. If you can get a trace, look for the sending sequence number being less than the receiving sequence number in both directions. This indicates that the two sides of the connection both think they are receiving duplicate packets, and then send immediate acknowlegments, which are also dropped as duplicates, and the cycle repeats. With a loopback connection, look at the two tcp control blocks. snd_nxt on block A will be less than rcv_nxt on block B, and vice versa. ( SR not found ) The problem is the user is unable to print the returned address from a recv call using a unix domain socket because there is no null terminator, and because the returned length is not the length of the string. ( SR number: 5003239517 ) Connections is tcp FIN_WAIT_2 state will eventually time out. Customer will see connections aborted with an error to the effect that "remote has aborted the connection". These errors would be returned only on very heavily loaded networks. ( SR number: 5000710814 ) An ENXIO error is presently passed from the transport layer up to the application error as a "hard", or irrecoverable error. It is left up to the application to decide how to handle this situation. This is incorrect, because ENXIO is generated by the driver(s) in situations which *may* be recoverable, such as the imfamous 82596 LAN chip error. The user will see applications fail with a connection failure error which may be accompanied by a log message from the driver indicating that some sort of hardware error has occurred. ( SR not found ) RFC 1323 is designed to accomodate LFP (large fat pipe) links, including ATM, Fibre Channel, and HIPPI. The changes made for this DTS will improve performance for these links and fix various bugs that arise in the course of using a link with a large MTU size. Note that there are two global variables which turn these changes on and off. BY DEFAULT THEY ARE OFF!!! These globals and their default values are as follows: tcp_dont_winscale = 1 tcp_dont_tsecho = 1 Yes, the default is one, and that means the enhancement is OFF. There is no error here. ( SR number: 1653119461 ) System panic with soo_rw, soclose on the stack. The panic would most likely be seen on 9.04 multiprocessor systems, but could be seen on any 9.X machine. fp->f_data pointer for the socket has been zeroed out, but the socket appears to be active and ok. ( SR number: 5003247148 ) ( SR number: 5003252148 ) ( SR number: 4701290205 ) A system hangs in an endless loop. This happens when we try to PEEK a socket with a oobmark not equal to zero (urgent data). The core dump will show soreceive as the last routine entered. ( SR number: 5003263541 ) ICMP 12 messages are passed to applications. some applications don't know what to do with them. ( SR number: 5003264713 ) The listen socket queue limit is only 20 and should be increased. The system administrator should be able to change the maximum. ( SR number: 5003264739 ) The problem is seen when we try to close a file with valid file pointer but invalid cred field. ( SR number: 1653134999 ) System panics when there are no lan i/fs configured, and nmget(GP_ip) is used to get "IP" MIB information. ( SR not found ) TCP/IP performance suffers on systems with a lot of listening and connected sockets. This is noticable on WWW servers which handle a lot of connection requests. ( SR number: 1653144972 ) There are cases where we can get FIN_WAIT_2 connections that never go away. We need a timer that customers can set to remove these connections. ( SR number: 5000712331 ) This defect will panic a system with corrupted memory. It will panic in different areas based on the memory that got currupted. ( SR number: 1653152611 ) A bad TCPOPT_MAXSEG TCP/IP option can cause a "Conditional trap" system panic. ( SR not found ) The problem is that a system panics in sbdrop(). ( SR number: 5003298554 ) The use of multiple IP addresses on the same system is partially broken. While setting up TCP connections, we fail to discriminate between sockets listening at the same port even though they use different IP addresses. This breaks Service Guard (which uses multiple IP addresses on the same interface) and some functionality of multihomed systems. This can also be seen as a bind() problem. ( SR not found ) ICMP Host Unreachable messages can cause a system panic. ( SR number: 4701313304 ) The current code allows one to create an arp entry on a poinnt to point interface. When the time expires on this entry,an attempt is made to build a packet by calling a procedure whose pointer should be in the arpcom table. In the point to point case, that pointer is NULL which causes a panic. ( SR number: 5003300319 ) When cksum is zero, it is not changed to 0xffff. (It should be). SR: 5003101527 4701218651 4701197269 1653055426 1653055103 5000695213 5003146415 4701223040 5003166975 4701237263 1653077800 5003170332 5003179093 4701253880 1653080929 5003185900 5003171686 4701253898 5003192807 4701249946 5003194134 4701253252 5003196360 5000707950 5003204222 5003216903 5003228270 1653109991 5003229070 5003229229 5003239517 5000710814 1653119461 5003247148 5003252148 4701290205 5003263541 5003264713 5003264739 1653134999 1653144972 5000712331 5003292979 1653152611 5003298554 4701313304 5003300319 5003314302 5003316810 5003318543 5003327973 5000716316 4701335554 1653163436 4701335596 5003342071 1653198069 4701350173 5003372144 Patch Files: /etc/conf/libinet.a(udp_usrreq.o) /etc/conf/libinet.a(tcp_usrreq.o) /etc/conf/libinet.a(tcp_timer.o) /etc/conf/libinet.a(tcp_subr.o) /etc/conf/libinet.a(tcp_output.o) /etc/conf/libinet.a(tcp_input.o) /etc/conf/libinet.a(raw_ip.o) /etc/conf/libinet.a(nm_udp.o) /etc/conf/libinet.a(nm_tcp.o) /etc/conf/libinet.a(nm_ip.o) /etc/conf/libhp-ux.a(nm_gen.o) /etc/conf/libinet.a(ip_output.o) /etc/conf/libinet.a(ip_mroute.o) /etc/conf/libinet.a(ip_input.o) /etc/conf/libinet.a(ip_igmp.o) /etc/conf/libinet.a(ip_icmp.o) /etc/conf/libinet.a(in_proto.o) /etc/conf/libinet.a(in_pcb.o) /etc/conf/libinet.a(in.o) /etc/conf/libinet.a(igmp_random.o) /etc/conf/libinet.a(if_ether.o) /etc/conf/libnet.a(route.o) /etc/conf/libnet.a(raw_cb.o) /etc/conf/libnet.a(nm_if.o) /etc/conf/libuipc.a(netisr.o) /etc/conf/libnet.a(if_ni.o) /etc/conf/libnet.a(if_loop.o) /etc/conf/libnet.a(if.o) /etc/conf/libhp-ux.a(dgram_aud.o) /etc/conf/libuipc.a(uipc_socket2.o) /etc/conf/libuipc.a(uipc_usrreq.o) /etc/conf/libuipc.a(uipc_domain.o) /etc/conf/libhp-ux.a(uipc_mbuf.o) /etc/conf/libuipc.a(uipc_socket.o) /etc/conf/libuipc.a(uipc_syscall.o) /etc/conf/libnipc.a(prb_name.o) /etc/conf/libnipc.a(nipc_syscall.o) what(1) Output: /etc/conf/libinet.a(udp_usrreq.o): PHNE_12399 udp_usrreq.c $Revision: 1.4.193.6 $ $Date : 97/01/15 11:04:35 $ /etc/conf/libinet.a(tcp_usrreq.o): PHNE_12399 tcp_usrreq.c $Revision: 1.5.193.15 $ $Dat e: 96/09/27 09:44:27 $ /etc/conf/libinet.a(tcp_timer.o): PHNE_12399 tcp_timer.c $Revision: 1.3.193.8 $ /etc/conf/libinet.a(tcp_subr.o): PHNE_12399 tcp_subr.c $Revision: 1.3.193.9 $ $Date: 96/03/20 13:22:18 $ /etc/conf/libinet.a(tcp_output.o): PHNE_12399 tcp_output.c $Revision: 1.3.193.6 $ $Date : 96/05/13 10:09:21 $ /etc/conf/libinet.a(tcp_input.o): PHNE_12399 tcp_input.c $Revision: 1.6.193.27 $ $Date : 97/09/04 12:16:58 $ /etc/conf/libinet.a(raw_ip.o): PHNE_12399 raw_ip.c $Revision: 1.2.193.2 $ /etc/conf/libinet.a(nm_udp.o): PHNE_12399 nm_udp.c $Revision: 1.2.193.2 $ /etc/conf/libinet.a(nm_tcp.o): PHNE_12399 nm_tcp.c $Revision: 1.1.193.2 $ /etc/conf/libinet.a(nm_ip.o): PHNE_12399 nm_ip.c $Revision: 1.3.193.2 $ /etc/conf/libhp-ux.a(nm_gen.o): PHNE_12399 nm_gen.c $Revision: 1.2.193.2 $ /etc/conf/libinet.a(ip_output.o): PHNE_12399 ip_output.c $Revision: 1.3.193.4 $ $Date: 95/10/30 14:32:27 $ /etc/conf/libinet.a(ip_mroute.o): PHNE_12399 ip_mroute.c $Revision: 1.3.193.2 $ /etc/conf/libinet.a(ip_input.o): PHNE_12399 ip_input.c $Revision: 1.3.193.10 $ $Date: 97/08/05 18:13:08 $ /etc/conf/libinet.a(ip_igmp.o): PHNE_12399 ip_igmp.c $Revision: 1.4.193.2 $ /etc/conf/libinet.a(ip_icmp.o): PHNE_12399 ip_icmp.c $Revision: 1.4.193.5 $ $Date: 9 5/10/30 14:32:24 $ /etc/conf/libinet.a(in_proto.o): PHNE_12399 in_proto.c $Revision: 1.2.193.2 $ $Date: 95/10/30 14:32:23 $ /etc/conf/libinet.a(in_pcb.o): PHNE_12399 in_pcb.c $Revision: 1.5.193.10 $ $Date: 9 6/09/13 15:46:36 $ /etc/conf/libinet.a(in.o): PHNE_12399 in.c $Revision: 1.4.193.8 $ $Date: 96/04/ 01 18:13:21 $ /etc/conf/libinet.a(igmp_random.o): PHNE_12399 igmp_random.c $Revision: 1.1.193.2 $ /etc/conf/libinet.a(if_ether.o): PHNE_12399 if_ether.c $Revision: 1.5.193.15 $ /etc/conf/libnet.a(route.o): PHNE_12399 route.c $Revision: 1.4.193.3 $ /etc/conf/libnet.a(raw_cb.o): PHNE_12399 raw_cb.c $Revision: 1.1.193.2 $ /etc/conf/libnet.a(nm_if.o): PHNE_12399 nm_if.c $Revision: 1.3.193.2 $ /etc/conf/libuipc.a(netisr.o): PHNE_12399 netisr.c $Revision: 1.7.193.5 $ /etc/conf/libnet.a(if_ni.o): PHNE_12399 if_ni.c $Revision: 1.5.193.3 $ $Date: 94/ 01/11 15:32:19 $ /etc/conf/libnet.a(if_loop.o): PHNE_12399 if_loop.c $Revision: 1.3.193.3 $ $Date: 9 4/05/27 10:02:22 $ /etc/conf/libnet.a(if.o): PHNE_12399 if.c $Revision: 1.2.193.2 $ /etc/conf/libhp-ux.a(dgram_aud.o): PHNE_12399 dgram_aud.c $Revision: 1.1.193.4 $ $Date: 94/05/24 09:36:23 $ /etc/conf/libuipc.a(uipc_socket2.o): PHNE_12399 uipc_socket2.c $Revision: 1.5.193.8 $ $Da te: 96/12/05 14:31:52 $ /etc/conf/libuipc.a(uipc_usrreq.o): PHNE_12399 uipc_usrreq.c $Revision: 1.4.193.7 $ /etc/conf/libuipc.a(uipc_domain.o): PHNE_12399 uipc_domain.c $Revision: 1.1.193.2 $ /etc/conf/libhp-ux.a(uipc_mbuf.o): PHNE_12399 uipc_mbuf.c $Revision: 1.5.193.4 $ $Date: 94/10/27 10:21:26 $ /etc/conf/libuipc.a(uipc_socket.o): PHNE_12399 uipc_socket.c $Revision: 1.6.193.12 $ $Da te: 97/06/05 14:09:21 $ /etc/conf/libuipc.a(uipc_syscall.o): PHNE_12399 uipc_syscall.c $Revision: 1.5.193.3 $ $Da te: 94/04/29 10:35:30 $ /etc/conf/libnipc.a(prb_name.o): PHNE_12399 prb_name.c $Revision: 1.4.193.5 $ /etc/conf/libnipc.a(nipc_syscall.o): PHNE_12399 nipc_syscall.c $Revision: 1.4.193.3 $ sum(1) Output: 16163 18 /etc/conf/libinet.a(udp_usrreq.o) 55394 22 /etc/conf/libinet.a(tcp_usrreq.o) 63171 11 /etc/conf/libinet.a(tcp_timer.o) 2101 18 /etc/conf/libinet.a(tcp_subr.o) 43598 13 /etc/conf/libinet.a(tcp_output.o) 50944 38 /etc/conf/libinet.a(tcp_input.o) 14118 9 /etc/conf/libinet.a(raw_ip.o) 47780 7 /etc/conf/libinet.a(nm_udp.o) 17903 9 /etc/conf/libinet.a(nm_tcp.o) 25104 20 /etc/conf/libinet.a(nm_ip.o) 25470 14 /etc/conf/libhp-ux.a(nm_gen.o) 52850 22 /etc/conf/libinet.a(ip_output.o) 22307 40 /etc/conf/libinet.a(ip_mroute.o) 7883 28 /etc/conf/libinet.a(ip_input.o) 33606 14 /etc/conf/libinet.a(ip_igmp.o) 27587 14 /etc/conf/libinet.a(ip_icmp.o) 29703 7 /etc/conf/libinet.a(in_proto.o) 32034 16 /etc/conf/libinet.a(in_pcb.o) 63097 18 /etc/conf/libinet.a(in.o) 57342 4 /etc/conf/libinet.a(igmp_random.o) 24291 73 /etc/conf/libinet.a(if_ether.o) 57512 16 /etc/conf/libnet.a(route.o) 1697 9 /etc/conf/libnet.a(raw_cb.o) 2928 10 /etc/conf/libnet.a(nm_if.o) 2976 16 /etc/conf/libuipc.a(netisr.o) 55351 20 /etc/conf/libnet.a(if_ni.o) 33257 12 /etc/conf/libnet.a(if_loop.o) 63027 14 /etc/conf/libnet.a(if.o) 55882 6 /etc/conf/libhp-ux.a(dgram_aud.o) 36094 32 /etc/conf/libuipc.a(uipc_socket2.o) 45539 21 /etc/conf/libuipc.a(uipc_usrreq.o) 17568 7 /etc/conf/libuipc.a(uipc_domain.o) 33390 29 /etc/conf/libhp-ux.a(uipc_mbuf.o) 58684 35 /etc/conf/libuipc.a(uipc_socket.o) 43254 26 /etc/conf/libuipc.a(uipc_syscall.o) 6707 24 /etc/conf/libnipc.a(prb_name.o) 39322 61 /etc/conf/libnipc.a(nipc_syscall.o) Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHNE_3579 PHNE_3657 PHNE_3939 PHNE_4587 PHNE_5010 PHNE_5361 PHNE_6227 PHNE_6707 PHNE_7252 PHNE_9028 PHNE_9100 Equivalent Patches: None Patch Package Size: 460 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. Copy the patch to your /tmp directory and unshar it: cd /tmp cp patch_source/PHNE_12399 . sh PHNE_12399 3. Become root and run update: /etc/update [-r [kernel_gen_file]] -s \ /tmp/PHNE_12399.updt PHNE_12399 Update moves the original software to /system/PHNE_12399/orig. Keep this file to recover from any potential problems. You should move the .text file to /system/PHNE_12399 for future reference. To put this patch on a magnetic tape and update from the tape drive, use dd: dd if=PHNE_12399.updt of=/dev/rmt/0m bs=2048 Special Installation Instructions: None