connecting to non-responding hosts: 1 hr timeout (fwd)

[Markus Friedl]

On Thu, May 03, 2001 at 12:34:23PM -0500, Dave Dykstra wrote:
> The alarm signal does not interrupt connect() on Linux (2.2.18 at least).
> It does interrupt connect() with an EINTR error on Solaris though (2.7 at
> least).  I'm not sure about other systems.

yes, i think i'm going to do a non-blocking connect,
just like i did in channels.c

-m