K 10
svn:author
V 4
stas
K 8
svn:date
V 27
2009-02-23T00:41:07.000000Z
K 7
svn:log
V 414
- Ruby socket connect code seems to work unstably in case if connection
  to remote host was refused. FreeBSD connect(2) call returns EINVAL in
  that case and clears the error code, so there's no way to determine
  what happened. Reimplement ruby_connect via select call instead of
  polling the status by connect(2). This may also reduce overhead (though,
  not verified).

Reported by:	Saku Ytti <saku@ytti.fi>

END