Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 27 Mar 2003 09:33:27 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Failed non-blocking connect returns incorrect errno on AF_UNIX protocol Message-ID: <20030327083327.GB23762@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3E80F8E1.2000409@linuxforum.net> <20030326085220.GQ23762@cygbert.vinschen.de> <3E8262B0.8070503@linuxforum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E8262B0.8070503@linuxforum.net> User-Agent: Mutt/1.4i On Thu, Mar 27, 2003 at 10:32:16AM +0800, David Huang wrote: > Corinna Vinschen wrote: > >I don't see that it's an error. On non-blocking sockets you have to > >expect that connect() returns before being connected. Just because > >other systems are so quick figuring out that nothing is listening on > >the other side, this doesn't invalidate the EINPROGRESS response under, > >well, slower conditions. > Well, in my test-case, /tmp/.afunix is a dead socket, connect must return > ECONNREFUSED but not EINPROGRESS, is it so? Yes, you're right but this information is missing in your previous posting. I see why this happens but I don't have a quick solution. However, thanks for the report, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/