From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <alpine.BSF.2.00.0911031125310.77218@legolas.yyc.orthanc.ca>
References: <55c52a87f0b8c0ac12a81a150f110b2b@brasstown.quanstro.net>
	<20091101184418.GM19125@gradx.cs.jhu.edu>
	<d1c554290911030730m64a7d415k23e5622510438b4f@mail.gmail.com>
	<alpine.BSF.2.00.0911031125310.77218@legolas.yyc.orthanc.ca>
Date: Tue,  3 Nov 2009 16:50:57 -0200
Message-ID: <d1c554290911031050k59c97eb6wbacdd5294e7c5994@mail.gmail.com>
From: Iruata Souza <iru.muzgo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [9fans] dtrace for plan 9
Topicbox-Message-UUID: 9678f590-ead5-11e9-9d60-3106f5b1d025

On Tue, Nov 3, 2009 at 4:29 PM, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>> i was told dtrace was non-intrusive at the time, but w2 would show the
>> command history from w1.
>
> More likely this is ksh sharing a history file.
>
>

at the time i couldn't reproduce it with other shells. anyway, iirc,
no such side-effect was seen without running dtrace (that still
doesn't say anything directly against dtrace, of course).