Date: Thu, 7 Jun 2001 15:09:17 -0400 From: Alfred Perlstein <bright@rush.net> To: Graham Barr <gbarr@pobox.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: read(2) and ETIMEDOUT Message-ID: <20010607150917.U1832@superconductor.rush.net> In-Reply-To: <20010607171501.S50444@pobox.com>; from gbarr@pobox.com on Thu, Jun 07, 2001 at 05:15:01PM %2B0100 References: <20010607171501.S50444@pobox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Graham Barr <gbarr@pobox.com> [010607 12:17] wrote: Since people seem to be helping you in other ways, I'll just answer this one: > So, here is my question. Does anyone know under what circumstance > ETIMEDOUT may be returned from read(2) or is this a potential bug > somewhere ? I'm quite sure ETIMEDOUT is a result of hitting the setsockopt SO_RCVTIMEO value when doing a read. -- -Alfred Perlstein [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010607150917.U1832>