From owner-freebsd-questions Thu Jul 19 9:32:43 2001 Delivered-To: freebsd-questions@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id AB09037B405 for ; Thu, 19 Jul 2001 09:32:39 -0700 (PDT) (envelope-from marcus@apfel.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id SAA29735 for freebsd-questions@freebsd.org; Thu, 19 Jul 2001 18:32:38 +0200 (CEST) Received: from marcus by apfel.sax.de with local (Exim 3.12 #1 (Debian)) id 15NGi2-0001sV-00 for ; Thu, 19 Jul 2001 18:31:30 +0200 Date: Thu, 19 Jul 2001 18:31:30 +0200 From: Marcus Obst To: freebsd-questions@freebsd.org Subject: close on non-blocking socket Message-ID: <20010719183130.A7106@apfel.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I am in doubt about the following; what happens when a non-blocking socket that still has pending outgoing data is closed? In my network book (by R. Stevens) I read that TCP will try to flush the data already queued in the output buffer. But in the FreeBSD man page of close I got: on the last close of a socket(2) associated naming information and queued data are discarded ~~~~~~~~~~~~~~~~~~~~~~~~~ What's right ...? P.S.: Please send the answer with CC to me, I'm currently not on the mailing list. Thank you.! Best regards from Dresden/Germany! Marcus -- Marcus Obst To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message