From owner-freebsd-hackers  Mon Aug  4 13:40:11 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA25863
          for hackers-outgoing; Mon, 4 Aug 1997 13:40:11 -0700 (PDT)
Received: from spoon.beta.com (root@[199.165.180.33])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA25858
          for <hackers@freebsd.org>; Mon, 4 Aug 1997 13:40:08 -0700 (PDT)
Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1])
	by spoon.beta.com (8.8.5/8.8.5) with ESMTP id QAA03104
	for <hackers@freebsd.org>; Mon, 4 Aug 1997 16:40:05 -0400 (EDT)
Message-Id: <199708042040.QAA03104@spoon.beta.com>
To: hackers@freebsd.org
Subject: SIGURG on ppp drop
Date: Mon, 04 Aug 1997 16:40:05 -0400
From: "Brian J. McGovern" <mcgovern@spoon.beta.com>
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Can I assume safely that if I am fetch'ing a file across a PPP link, and
that link goes down (thereby removing the route, and causing a "No
route to host" error message when pinging) that the fetch process will
receive a SIGURG? 

I'm curious, because I'm running some tests that require fetch to die if
the link goes down, and I want to try to catch SIGURG, and then "cleanup
and exit"(tm).
	-Brian