Newsgroups: comp.sys.amiga.tech
Path: utzoo!utgpu!watserv1!maytag!watdragon!lion!sjorr
From: sjorr@lion.uwaterloo.ca (Stephen Orr)
Subject: Re: Help! Need LOGFILE utility!!
Message-ID: <1990Oct30.051428.2549@watdragon.waterloo.edu>
Sender: daemon@watdragon.waterloo.edu (Owner of Many System Processes)
Organization: University of Waterloo
References: <10007@milton.u.washington.edu> <399@ra.abo.fi> <10205@milton.u.washington.edu>
Distribution: na
Date: Tue, 30 Oct 90 05:14:28 GMT
Lines: 20

In article <10205@milton.u.washington.edu> dsheythe@milton.u.washington.edu (Donald Sheythe) writes:
>
>
>Here's the best suggestion I've gotten so far (though I haven't tried CB yet):
>
>The DCMD utility (Thanks, Matt Dillon!) works well for capturing
>CLI I/O.
>
>However, there are a couple of problems.  Unless your input is
>echoed to the terminal, it won't be captured in the log file.  
>
The last time I used CB for this purpose it handled grabbing the input
just fine. It even dealt cleanly with me editing the input (ie using bs
and del) which is surprising given that it captures out to the rastport.

					Stephen Orr
					SandIsoft
---
too lazy to .sig
---