From owner-freebsd-current@FreeBSD.ORG  Thu Apr 10 15:18:48 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 40F4A37B401
	for <current@freebsd.org>; Thu, 10 Apr 2003 15:18:47 -0700 (PDT)
Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net
	[207.217.120.188])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E99E343FA3
	for <current@freebsd.org>; Thu, 10 Apr 2003 15:18:46 -0700 (PDT)
	(envelope-from tlambert2@mindspring.com)
Received: from pool0274.cvx40-bradley.dialup.earthlink.net ([216.244.43.19]
	helo=mindspring.com)
	by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128)
	(Exim 3.33 #1)	id 193kNZ-0004ss-00; Thu, 10 Apr 2003 15:18:45 -0700
Message-ID: <3E95ED19.7512ECF6@mindspring.com>
Date: Thu, 10 Apr 2003 15:15:53 -0700
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: BelletJr@aol.com
References: <109.225ca595.2bc723f2@aol.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4c964df480dfbc21cd416561ae5c8486a387f7b89c61deb1d350badd9bab72f9c350badd9bab72f9c
cc: current@freebsd.org
Subject: Re: connect(2) behavior with unreacheable hosts
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2003 22:18:48 -0000

BelletJr@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