Re: connect(2) behavior with unreacheable hosts

From: Terry Lambert <tlambert2_at_mindspring.com>
Date: Thu, 10 Apr 2003 15:15:53 -0700
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
Received on Thu Apr 10 2003 - 13:18:48 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:03 UTC