Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 19 Jun 2001 18:58:55 +0300 Message-Id: <200106191558.SAA24155@linux.> From: "Ehud Karni" To: "\"\"David A. Cobb\"\"" Subject: Re: One dumb question CC: cygwin@cygwin.com In-reply-to: <5.1.0.14.0.20010618114229.03d27610@mail> (message from David A. Cobb on Mon, 18 Jun 2001 11:46:39 -0400) Organization: Simon & Wiesel Insurance agency Reply-to: ehud@unix.simonwiesel.co.il References: <5.1.0.14.0.20010618114229.03d27610@mail> X-Mailer: Emacs 20.7.1 rmail (send-msg 1.104) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 7bit On Mon, 18 Jun 2001 11:46:39 -0400, David A. Cobb wrote: > Is there a way to get the "current" bash shell to tee its output to a > logfile? I remember doing something like this once upon a time but I don't > recall what I did and I was using a different shell (ksh on an HP/UX). You can achieve it by the following 3/4 commands: exec 3>&1 # create pipe (copy of stdout) exec 1>bash.dbg # direct stdout to file ## exec 2>&1 # uncomment if you want stderr too tail -f bash.dbg >&3 & # run tail in bg If you don't redirect stderr, the order of stdout and stderr messages may be out of original order. Here is a sample script that tested this on both Linux and Cygwin. #! /bin/sh -ex exec 3>&1 exec 1>bash.dbg exec 2>&1 tail -f bash.dbg >&3 & : rest of script echo "aaa bbb ccc" : "stderr only" sleep 5 echo "ddd eee fff" ########### end of test ########### Ehud. -- Ehud Karni Mivtach - Simon Insurance /"\ Tel: +972-3-6212-757 Fax: +972-3-6292-544 \ / ASCII Ribbon Campaign (USA) Fax and voice mail: 1-815-5509341 X Against HTML Mail Better Safe Than Sorry / \ mailto:ehud@unix.simonwiesel.co.il http://www.simonwiesel.co.il -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple