Date: Thu, 19 Jul 2001 22:01:31 +0100 From: Richard Smith <rdls@satamatics.com> To: Marcus Obst <mobst@apfel.sax.de> Cc: freebsd-questions@freebsd.org Subject: Re: close on non-blocking socket Message-ID: <20010719220131.A1027@gaia.home.rdls.net> In-Reply-To: <20010719183130.A7106@apfel.sax.de>; from mobst@apfel.sax.de on Thu, Jul 19, 2001 at 06:31:30PM %2B0200 References: <20010719183130.A7106@apfel.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 19, 2001 at 06:31:30PM +0200, Marcus Obst wrote: > 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 ...? The behaviour of close(2) in this case, is modified by SO_LINGER (see getsockopt(2)). Richard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010719220131.A1027>