mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Patrick Mau <mau@oscar.prima.de>
To: Dan Kegel <dank@kegel.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: connect() to localhost non-blocking.
Date: Mon, 22 Oct 2001 17:49:59 +0200	[thread overview]
Message-ID: <20011022174959.A31147@oscar.dorf.de> (raw)
In-Reply-To: <3BD357B2.12AE9A5E@kegel.com>
In-Reply-To: <3BD357B2.12AE9A5E@kegel.com>

On Sun, Oct 21, 2001 at 04:18:10PM -0700, Dan Kegel wrote:
> > Patrick Mau <mau@oscar.prima.de> writes:
> > 

[Snip]

> You have to be prepared to handle both immediate and delayed
> connection, especially if you want to be portable.  (Solaris behaves 
> a bit differently than Linux in this regard.)  See
> http://www.kegel.com/dkftpbench/dkftpbench-0.37/ftp_client_pipe.cc
> for an example of how to handle nonblocking connects more or less portably.
> (You have to wade through quite a bit of code, tabstops 4, to find
> all the connect-handling stuff -- sorry.)
> - Dan

Hallo Dan,

thnaks for the pointer and your remarks, but I really
wondered if linux _never_ immediatly accept()'s connections.

I never saw a connect() call returning 0 (connected) on a
non-blocking socket. Always EINPROGRESS. I guess I have to
look at the kernel to see scheduling effects ...

thanks,
Patrick

  reply	other threads:[~2001-10-22 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-21 23:18 Dan Kegel
2001-10-22 15:49 ` Patrick Mau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-21 20:42 Patrick Mau
2001-10-21 21:00 ` Doug McNaught

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=20011022174959.A31147@oscar.dorf.de \
    --to=mau@oscar.prima.de \
    --cc=dank@kegel.com \
    --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®