[haiku-bugs] Re: [Haiku] #2963: select() doesn't wait after non-blocking connect()
- From: "pulkomandy" <trac@xxxxxxxxxxxx>
- Date: Wed, 08 Jan 2014 16:57:51 -0000
#2963: select() doesn't wait after non-blocking connect()
--------------------------------------+---------------------------
Reporter: bonefish | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: Network & Internet/TCP | Version: R1/pre-alpha1
Resolution: | Keywords:
Blocked By: | Blocking:
Has a Patch: 0 | Platform: All
--------------------------------------+---------------------------
Comment (by pulkomandy):
ping?
Apparently the lockup problems we have in Web+ are because things are
waiting for too long on a connect(). Trying to close the socket while it
is connect()ing doesn't unlock the connect call, so we wait for the whole
75 seconds timeout on that (things works better for unlocking read() and
write()).
I wanted to try using non-blocking mode and waiting on a select() for the
connection to actually happen, hoping that closing the socket would unlock
select(). But select doesn't block at all, so that solution can't work.
--
Ticket URL: <http://dev.haiku-os.org/ticket/2963#comment:2>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
