in reply to Redirecting STDERR output to file in the cpan shell

cmd.exe, and the cpan shell, on Windows is strangely like most UNIX shells (not csh) in this syntax:
cpan install fred >install_log.txt 2>&1

[download]
Unfortunately you then cannot see any output, because it is all going to a file! So, it might be better to pipe output (and stderr) to a pipe:
cpan install fred 2>&1|more

[download]
Again, this is the same as most UNIX shells, except csh.

Replies are listed 'Best First'.
Re^2: Redirecting STDERR output to file in the cpan shell
by lancer (Scribe) on Dec 02, 2010 at 12:51 UTC

    Thank you cdarke, this is even closer to what I originally intended to do.

    I didn't know the "cpan" tool could be invoked by itself from the command line. It does work however, and from there it's possible to redirect STDERR and STDOUT to a file with the cmd shell, exactly as you specified in your example.

    Now I got the output into a file, and it's over 30Kb's long.

    Piping into the "more" utility also works, but it's a lot less useful than "less" on Linux. But still, it's good to know that this technique exists.

    Have a nice day! :)

[reply]
      It sometimes helps to pipe to "tee" (see linux command, man tee) the output so that it still appears on your console, but you can capture it. This way if there's any interractive input required by the script you can see the prompts. The 2>&1 directive tells the shell to send STDERR to the same place as STDOUT, that's for the bash shell. For C shell the equivalent redirective would be  >& or for pipe |&.
[reply]
[d/l]
[select]
[reply]

In Section Seekers of Perl Wisdom