Xref: utzoo comp.sources.wanted:9432 alt.sources.wanted:25
Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!rutgers!cbmvax!kevin
From: kevin@cbmvax.UUCP (Kevin Klop)
Newsgroups: comp.sources.wanted,alt.sources.wanted
Subject: Re: separate redirection of stderr and stdout in csh.
Message-ID: <8607@cbmvax.UUCP>
Date: 17 Nov 89 07:44:19 GMT
References: <13928@teraida.UUCP>
Reply-To: kevin@cbmvax.UUCP (Kevin Klop)
Organization: Commodore Technology, West Chester, PA
Lines: 22

In article <13928@teraida.UUCP> jeffy@teraida.UUCP (Jeffrey Youngstrom) writes:
>Hiya,
>	In the bourne shell I can do this:
>
>		#!/bin/sh
>
>		dumb_command 1> good_stuff 2> errors
>
>	to send the output of my command to good_stuff, and
>	any error messages to a file called errors.
>
>	How the heck do you do this for csh?!!!
>
>	And don't say "well it's easy if you use perl"!!! :-)

well, dumb_command >&somestuff

will redirect stderr out to somestuff.  It has the unfortunate side effect
of ALSO redirecting stdout as well.  I don't believe that there's a way
to affect this.

                              -- Kevin Klop --