( ESNUG 359 Item 8 ) --------------------------------------------- [9/13/00]
From: "Robert Wiegand" <rwiegand@nxtwavecomm.com>
Subject: Workaround For A Little Control-C "dc_shell | tee logfile" Gotcha
Hi John,
I got hit by a little gotcha recently that I thought I should share.
I've got into the habbit of using the "dc_shell | tee logfile" syntax for
interactive debugging so I can have a logfile for the session. One nice
thing about interactive sessions, is that a control-C will allow you to
checkpoint, or stop something that is compiling into oblivion and see what's
wrong. This may be very obvious to some, but I found out the hard way that
when using the " | tee" syntax, the control-C is passed to the "tee" instead
of the dc_shell session. This basically breaks the pipe and stops the job,
with no way that I could find to recover. Any UNIX gurus out there know
how to recover if this happens? To prevent this from happening, make sure
to use the -i switch on tee, which tells it to ignore interrupts as follows:
"dc_shell | tee -i logfile"
This allows the use of control-C for dc_shell.
- Bob Wiegand
NxtWave Communications Langhorne, PA
|
|
