From owner-freebsd-hackers Sun Dec 8 05:43:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id FAA09350 for hackers-outgoing; Sun, 8 Dec 1996 05:43:04 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id FAA09344 for ; Sun, 8 Dec 1996 05:43:01 -0800 (PST) Message-Id: <199612081343.FAA09344@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA089932551; Mon, 9 Dec 1996 00:42:31 +1100 From: Darren Reed Subject: Re: truss, trace ?? To: proff@suburbia.net Date: Mon, 9 Dec 1996 00:42:31 +1100 (EDT) Cc: avalon@coombs.anu.edu.au, hackers@freebsd.org In-Reply-To: <19961208072846.9917.qmail@suburbia.net> from "proff@suburbia.net" at Dec 8, 96 06:28:46 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from proff@suburbia.net, sie said: > > > > > 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 and make sure you don't fill your filesystem.... Darren