Xref: utzoo comp.sources.wanted:9569 alt.sources.wanted:45 Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!gem.mps.ohio-state.edu!usc!apple!oliveb!mipos3!omepd!merlyn From: merlyn@iwarp.intel.com (Randal Schwartz) Newsgroups: comp.sources.wanted,alt.sources.wanted Subject: Re: separate redirection of stderr and stdout in csh. Message-ID: <5267@omepd.UUCP> Date: 27 Nov 89 16:18:55 GMT References: <13928@teraida.UUCP> <690@fylz.UUCP> Sender: news@omepd.UUCP Reply-To: merlyn@iwarp.intel.com (Randal Schwartz) Followup-To: comp.sources.wanted Organization: Stonehenge; netaccess via Intel, Hillsboro, Oregon, USA Lines: 21 In-reply-to: deven@rpi.edu (Deven T. Corzine) In article , deven@rpi (Deven T. Corzine) writes: | | As many people pointed out, the following works: | | (dumb_command > good_stuff) >& errors | | However, I don't believe it is possible to redirect stderr while | piping stdout to another command... (Yes, you could put the entire | pipeline in a subshell, but you can't have just one command from the | pipeline have its stderr split away...) Sure you can. Lean on /bin/sh -- % comm1 arga argb | /bin/sh -c 'comm2 arga argb 2>errors' | comm3 arga argb "Magic is easy, once *you* know the secret..." :-) -- /== Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ====\ | on contract to Intel's iWarp project, Hillsboro, Oregon, USA, Sol III | | merlyn@iwarp.intel.com ...!uunet!iwarp.intel.com!merlyn | \== Cute Quote: "Welcome to Oregon... Home of the California Raisins!" ==/ Brought to you by Super Global Mega Corp .com