From owner-freebsd-questions Mon Jul 17 12:18:50 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA17851 for questions-outgoing; Mon, 17 Jul 1995 12:18:50 -0700 Received: from fslg8.fsl.noaa.gov (fslg8.fsl.noaa.gov [137.75.131.171]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA17843 for ; Mon, 17 Jul 1995 12:18:48 -0700 Received: by fslg8.fsl.noaa.gov (5.57/Ultrix3.0-C) id AA13951; Mon, 17 Jul 95 13:18:44 -0600 Received: by emu.fsl.noaa.gov (1.38.193.4/SMI-4.1 (1.38.193.4)) id AA29717; Mon, 17 Jul 1995 13:21:59 -0600 Date: Mon, 17 Jul 1995 13:21:59 -0600 From: kelly@fsl.noaa.gov (Sean Kelly) Message-Id: <9507171921.AA29717@emu.fsl.noaa.gov> To: archie@bubba.tribe.com Cc: questions@freebsd.org In-Reply-To: <199507171806.LAA03018@bubba.tribe.com> (message from Archie Cobbs on Mon, 17 Jul 1995 11:06:52 -0700 (PDT)) Subject: Re: Viewing output of "tun" driver Sender: questions-owner@freebsd.org Precedence: bulk >>>>> "Archie" == Archie Cobbs writes: Archie> Then in one window I said: Archie> hexdump < /dev/tun0 Archie> But then when I try to kill the "hexdump" process, I find Archie> that it's stuck in uninterruptable disk wait and simply Archie> cannot be killed (ie, even kill -9 doesn't work): I think the kill signal will eventually be delivered if you can get some new output to go along /dev/tun0, thereby getting hexdump out of D-wait. That is, kill ping would make the hexdump go away. Of course, so would rebooting, power cycling, etc. -- Sean Kelly NOAA Forecast Systems Lab, Boulder Colorado USA People think it would be fun to be a bird because you could fly. But they forget the negative side, which is the preening. -- Jack Handey