Msys: how to keep STDERR on the screen and at the same time copy both STDOUT and STDERR to files

Question

I would like to be able to

For information, I am using Msys to do that.

.

After doing some research on the SO, I have tried to use something like

<my command> > >(tee stdout.log) 2> >(tee stderr.log)

Bu I got the following error:

sh: syntax error near unexpected token `>'

.

Any idea on how to do that?

score 1 · Answer 1 · edited May 23 '17 at 10:34

1

I have a simple script (test.sh) that generates STDOUT and STDERR:

#!/bin/bash
echo hello
rm something 
exit

Then, to do what you want execute with the following:

./test.sh > stdout.log 2> >(tee stderr.log >&2)

You'll get the STDERR on the screen, and two separated log files with STDERR and STDOUT. I used part of the answer given here

Note that I am assuming you don't have a file called something on the current directory :)

If you want both STDOUT and STDERR to go to the same file, use the -a option on tee:

./test.sh > std.log 2> >(tee -a std.log >&2)

edited May 23 '17 at 10:34

Community

answered Jun 17 '16 at 18:48

Vinicius Placco

Thanks for the answer although it might not work on MSys but just on Cygwin or shell. Where are you running this shell conmand? – Jean-Francois T. Jun 20 '16 at 02:24
I ran this on a MAC OS terminal in `bash`. I am not sure about running on MSYS. – Vinicius Placco Jun 20 '16 at 12:57
... unfortunately not working in Msys, as I mentioned. Probably works in Cygwin though. – Jean-Francois T. Jun 21 '16 at 07:25

score 1 · Accepted Answer · answered Jun 21 '16 at 07:33

1

There might be no direct solution in Msys but the >(tee ... ) solution works fine in *Nix, OSX, and probably Cygwin.

The workaround is to grep all the errors and warnings we want to keep them on the screen.

I have successfully used the following command for a makefile to compile C code:

answered Jun 21 '16 at 07:33

Jean-Francois T.

That is a good workaround. Could you, instead of using `grep -E` to get STDERR, use `grep -v` to exclude STDOUT and get everything else? Well, that assumes you know what the STDOUT is, which may not be the case. – Vinicius Placco Jun 21 '16 at 12:28
@ViniciusPlacco: provided you know what would be in STDOUT, you can definitely use `grep -v` ... point is, a pattern on errors and warnings is much easier :) – Jean-Francois T. Jun 22 '16 at 03:47
Fair enough :) Good to have both in the pocket. Thanks! – Vinicius Placco Jun 22 '16 at 10:09

2 Answers2