connect(2) behavior with unreacheable hosts

[Terry Lambert]

BelletJr at aol.com wrote:
> Why does not connect(2) return any error when trying to connect to a host
> unreachable because of an infinite loop in the routes? No time-out occurs and
> the value 0 is returned by connect(2).
> My test was done with TCP/IPv4.

Because it can't detect an infinite routing loop.

The timeout is the responsibility of the application; see
"man alarm" and "man signal" for more information.

-- Terry