From owner-freebsd-current  Wed Jun 19 05:15:49 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id FAA10009
          for current-outgoing; Wed, 19 Jun 1996 05:15:49 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA09998
          for <freebsd-current@freebsd.org>; Wed, 19 Jun 1996 05:15:39 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id WAA14502; Wed, 19 Jun 1996 22:07:51 +1000
Date: Wed, 19 Jun 1996 22:07:51 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199606191207.WAA14502@godzilla.zeta.org.au>
To: fcurrent@jraynard.demon.co.uk, wosch@cs.tu-berlin.de
Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems]
Cc: freebsd-current@freebsd.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>Indeed. Apart from volume of output, is there any particular reason
>>why ktrace writes to a file which kdump reads in, as opposed to using
>>a pipe? Particularly as the first thing kdump does is 
>>freopen(tracefile, "r", stdin)!

>Hm, try `ktrace -f /dev/stdout | kdump -f /dev/stdin'

I tried it before posting :-).  ktrace(2) only works on regular files.  This
is undocumented of course.  It obviously can't work on stdout because stdout
goes away when ktrace(1) exits.

Bruce