On Wed, 8 Aug 2001, Michael Schwendt wrote:
> On 2001-08-07, [EMAIL PROTECTED] wrote:
>
> >Understood, but he said he's using startx 2&>1 | tee xwinlog and we are
> >saying to use startx 2>&1 | tee winlog (or shorter way, startx >& |tee
> >xwinlog) which would account for him not getting anything in his
> >xwinlog, no?
>
> Yes. :) As has been pointed out before, 2&>1 is wrong and does not
> direct stderr to stdout, so stderr is not captured. But 2>&1 does.
> So does >&.
and just in case you want to set up a pipe for *only* the error
messages, you can do neat stuff like:
$ cmd1 2>&1 >outfile | cmd2
with the above, stdout from cmd1 goes to outfile, while stderr *only*
gets piped thru to cmd2.
rday
--
Robert P. J. Day
Eno River Technologies, Durham NC
Unix, Linux and Open Source training
"This is Microsoft technical support. How may I misinform you?"
I ask for so little. And boy, do I get it.
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
