Alan,<div><br></div><div>Thank you for your help.</div><div><br></div><div>Sorry to bother you with such a trivial &quot;problem&quot;. I&#39;m still learning &quot;unix&quot; after all these years. Sigh.</div><div><br></div>
<div>Have a GREAT weekend and, again, Thanks.</div><div><br></div><div>George...<br><br><div class="gmail_quote">On Fri, Apr 1, 2011 at 3:41 PM, Alan Curry <span dir="ltr">&lt;<a href="mailto:pacman-cu@kosh.dhis.org">pacman-cu@kosh.dhis.org</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">George Goffe writes:<br>
&gt; Alan,<br>
&gt;<br>
&gt; Oops. I goofed... My apologies.<br>
&gt;<br>
&gt; The example would be this &quot;somescript | tee somescript.log 2&gt;&amp;1&quot;.<br>
&gt;<br>
&gt; The intent is to capture all the output (stdout and stderr) from<br>
&gt; &quot;somescript&quot;. &quot;somescript&quot; runs several commands that may or may not utilize<br>
&gt; other FDs. I was hoping to get a better output than what you might get from<br>
&gt; the script command which records all the messages + a ton of other things<br>
&gt; like escapes which are a pain to eliminate.<br>
&gt;<br>
&gt; Does this make better sense?<br>
<br>
</div>Well, you still have the 2&gt;&amp;1 in the wrong place. If you want it to affect<br>
the stderr of the command to the left of the pipe, you have to put it to the<br>
left of the pipe.<br>
<br>
</blockquote></div><br></div>