From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from cpe-144-136-137-64.qld.bigpond.net.au ([144.136.137.64] helo=data.home ident=mail) by speech.braille.uwo.ca with esmtp (Exim 3.35 #1 (Debian)) id 17vTtX-0007nw-00 for ; Sat, 28 Sep 2002 22:33:19 -0400 Received: from geoff (helo=localhost) by data.home with local-esmtp (Exim 3.12 #1 (Debian)) id 17vTtY-0001Of-00 for ; Sun, 29 Sep 2002 12:33:20 +1000 Date: Sun, 29 Sep 2002 12:33:20 +1000 (EST) From: Geoff Shang To: speakup@braille.uwo.ca Subject: Re: Bastille In-Reply-To: <20020929020210.GC4236@lrxms.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: On Sat, 28 Sep 2002, Scott Howell wrote: > can't captured the errors its generating in the scripts cause they just > scroll off the screen. Is there a way to capture these? The error log it > generates isn't giving me any useful data. You can do this by redirecting standard error, either to standard out or to a file. Some examples: 2>&1 redirects standard error to standard output. This means you can do commands like: 2>&1 |more or 2>&1 >filename.log to capture everything. This is mainly useful when you need to see errors in context, such as with a compilation. If you only want to log the errors, you can do: 2>filename.log Using this logic, you can make a program only display the errors with no regular output by doing >/dev/null since you've only redirected standard output, standard error will still be seen. Hope this helps. Geoff.