From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dan Kegel <dank@kegel.com>
Cc: david.madore@ens.fr,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: re: interrupting connect(), EINTR, EINPROGRESS, EALREADY, and so on
Date: 25 Apr 2003 09:33:45 +0100 [thread overview]
Message-ID: <1051259624.5459.4.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3EA8CA5E.7030102@kegel.com>
On Gwe, 2003-04-25 at 06:40, Dan Kegel wrote:
> David Madore wrote:
> > http://www.eleves.ens.fr:8080/home/madore/computers/connect-intr.html
> Interesting.
>
> I'd suggest bringing this up on the austin-group-l list,
> see http://www.opengroup.org/austin/lists.html
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
next prev parent 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 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1051259624.5459.4.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dank@kegel.com \
--cc=david.madore@ens.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
all inboxes | Powered by JetHome®