From owner-freebsd-hackers  Thu Sep  4 08:59:10 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id IAA07618
          for hackers-outgoing; Thu, 4 Sep 1997 08:59:10 -0700 (PDT)
Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA07601
          for <hackers@freebsd.org>; Thu, 4 Sep 1997 08:59:05 -0700 (PDT)
Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id LAA26725 for <hackers@freebsd.org>; Thu, 4 Sep 1997 11:58:21 -0400 (EDT)
Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1])
	by bmcgover-pc.cisco.com (8.8.5/8.8.5) with ESMTP id LAA19312
	for <hackers@freebsd.org>; Thu, 4 Sep 1997 11:57:35 -0400 (EDT)
Message-Id: <199709041557.LAA19312@bmcgover-pc.cisco.com>
To: hackers@freebsd.org
Subject: Getting FTP to die when route disappears
Date: Thu, 04 Sep 1997 11:57:35 -0400
From: Brian McGovern <bmcgover@cisco.com>
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I'm currently using several FreeBSD boxes to test file transfers to routers
under test. The problem that I'm having is that if a call drops, and the
route is deleted from the routing table, the FTP client just zones out, 
waiting for the transfer to complete (I had one hang for ~ 2 days). Is
there any way to make it so if a route drops (ie - ping
reports "No route to host") to get FTP to realize it's route is down, and
abort the transfer? Thanks.
	-Brian