archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <>
To: Dan Kegel <>
	Linux Kernel Mailing List <>
Subject: re: interrupting connect(), EINTR, EINPROGRESS, EALREADY, and so on
Date: 25 Apr 2003 09:33:45 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Gwe, 2003-04-25 at 06:40, Dan Kegel wrote:
> David Madore wrote:
>  >
> Interesting.
> I'd suggest bringing this up on the austin-group-l list,
> see

Linux is perhaps a little friendlier but it isnt clear. The socket api
drafts have an even more fun bug. For some protocols "bind" is a
blocking operation but the API was written by someone who never
considered this

  reply	other threads:[~2003-04-25  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25  5:40 interrupting connect(), EINTR, EINPROGRESS, EALREADY, and so on Dan Kegel
2003-04-25  8:33 ` Alan Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-25  4:24 David Madore

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).