archive mirror
 help / color / mirror / Atom feed
From: David Madore <>
Subject: interrupting connect(), EINTR, EINPROGRESS, EALREADY, and so on
Date: Fri, 25 Apr 2003 06:24:12 +0200	[thread overview]
Message-ID: <> (raw)


I hope this is not too off-topic for this list.  I have discovered
discrepancies between various Unix implementations and/or their
documentation, and the Single Unix Specification, concerning the
behavior of the connect() system call for blocking, stream, sockets,
when it is interrupted by a signal.  Rather than explain it all, I'll
refer you to the Web page I just wrote about this, namely <URL:

I believe that the behavior Linux uses is the best, but it seems to be
at odds with a literal reading of the Specification.  (Details and
explanations are on the page I've just mentioned.)  I'd like to know a
little more about this, e.g., how it was decided and by whom, and
when, and what arguments can be given to support it.

     David A. Madore
    (, )

             reply	other threads:[~2003-04-25  4:12 UTC|newest]

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

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).