From owner-freebsd-hackers Sat Jul 12 15:46:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23489 for hackers-outgoing; Sat, 12 Jul 1997 15:46:39 -0700 (PDT) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23484 for ; Sat, 12 Jul 1997 15:46:35 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.5/8.8.5) with SMTP id SAA10617 for ; Sat, 12 Jul 1997 18:47:06 -0400 (EDT) Date: Sat, 12 Jul 1997 18:47:06 -0400 (EDT) From: "David E. Cross" To: hackers@freebsd.org Subject: Re: TCP bug in 2.2 In-Reply-To: <199707122153.OAA28921@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 12 Jul 1997, Terry Lambert wrote: > 3) The client software was ported from a sane TCP/IP environment, > like UNIX, and the programmers have no idea that "shutdown()" > is supposed to be called (amazingly enough, on UNIX systems, > calling "shutdown()" shuts the machine down... who would have > ever thought of naming a function for what the function does? > Apparently not the originators of Winsock.). The library call shutdown(2) is used to 'shut down' part of a full-duplex socket, you can in essence close() a connection with shutdown(2). -- David Cross