[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: non-blocking connect()
From: |
山本和彦 |
Subject: |
Re: non-blocking connect() |
Date: |
Mon, 01 Nov 2004 23:51:26 +0900 (JST) |
> > I'm not sure but I guess this patch does not solve the problem
>
> Can you try it, please.
I will send your patch to friends since I cannot reproduce this
phenomenon recently. The friends uses NetBSD on VMWare and the problem
still appear occasionally in that circumstance.
> > the second connect(2) is probably interrupted again.
>
> Can you determine what those interrupts are?
Sorry, no. The following is ktrace on NetBSD when I used to reproduce
the problem.
17374 emacs CALL socket(2,1,6)
17374 emacs RET socket 3
...
17374 emacs CALL connect(3,0x86c2720,0x10)
17374 emacs RET connect -1 errno 4 Interrupted system call
...
17374 emacs CALL connect(3,0x86c2720,0x10)
17374 emacs RET connect -1 errno 37 Operation already in progress
errno 4 is EINTR.
errno 37 is EALREADY.
This is everything I know.
P.S.
>From my experience, when open-network-connection() fails on NetBSD,
the next open-network-connection() also fails. This means trying
connect(2) with another socket failed. What's why I said your patch
would not solve the problem.
--Kazu
- Re: non-blocking connect(), Han Boetes, 2004/11/01
- Re: non-blocking connect(), Kim F. Storm, 2004/11/01
- Re: non-blocking connect(), 山本和彦, 2004/11/01
- Re: non-blocking connect(), Kim F. Storm, 2004/11/01
- Re: non-blocking connect(),
山本和彦 <=
- Re: non-blocking connect(), 山本和彦, 2004/11/02
- Re: non-blocking connect(), 山本和彦, 2004/11/08
- Re: non-blocking connect(), Kim F. Storm, 2004/11/09
- Re: non-blocking connect(), 山本和彦, 2004/11/10