Path: utzoo!attcan!uunet!mailrus!wuarchive!udel!udccvax1!pricked
From: pricked@vax1.acs.udel.EDU (Jenn-Ming Yang)
Newsgroups: comp.sources.wanted
Subject: Re: separate redirection of stderr and stdout in csh.
Message-ID: <5048@udccvax1.acs.udel.EDU>
Date: 17 Nov 89 14:13:30 GMT
References: <13928@teraida.UUCP> <8607@cbmvax.UUCP>
Reply-To: pricked@vax1.acs.udel.EDU (Jenn-Ming Yang)
Organization: University of Delaware
Lines: 34

In article <8607@cbmvax.UUCP> kevin@cbmvax.UUCP (Kevin Klop) writes:
>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.

Sure is(at least on BSD 4.3 unix, no access to other unix types)

   (dumb_command > goodstuff) >& errors

ALL stdout goes to 'goodstuff', ALL stderr goes to 'errors'.
You can do it using pipes also.

I didn't see my earlier post. Maybe it got sucked away by a blackhole.






-- 
Send e-mail to:
pricked@vax1.acs.udel.edu (or pricked@192.5.57.1, pricked@192.5.57.129)
!!!!!!!!!!!!!!!!!!!!!!!!There is no substitute!!!!!!!!!!!!!!!!!!!!!!!!!
!!played lums pond? why not? are you weak or do you just have brains?!!