From owner-freebsd-hackers  Sat Dec  7 23:29:12 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id XAA00476
          for hackers-outgoing; Sat, 7 Dec 1996 23:29:12 -0800 (PST)
Received: from pdx1.world.net (pdx1.world.net [192.243.32.18])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA00471
          for <hackers@freebsd.org>; Sat, 7 Dec 1996 23:29:10 -0800 (PST)
From: proff@suburbia.net
Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id XAA06432 for <hackers@freebsd.org>; Sat, 7 Dec 1996 23:29:32 -0800 (PST)
Received: (qmail 9918 invoked by uid 110); 8 Dec 1996 07:28:46 -0000
Message-ID: <19961208072846.9917.qmail@suburbia.net>
Subject: Re: truss, trace ??
In-Reply-To: <199612080150.RAA20512@freefall.freebsd.org> from Darren Reed at "Dec 8, 96 12:50:03 pm"
To: avalon@coombs.anu.edu.au (Darren Reed)
Date: Sun, 8 Dec 1996 18:28:46 +1100 (EST)
Cc: hackers@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > Be nice if there was an option for it to output (immeadiately) to stdout
> > > rather than ktrace.out.
> > 
> > I'm afraid that the kernel risks to stall if you get it to write the
> > trace into a FIFO.  But perhaps it's not too difficult to have
> > kdump(8) doing some `tail -f' like magic?  This should effectively
> > yield you a similar behaviour.

ktrace ./foo & kdump -l