in reply to Re: Re: Re: Can't spawn "cmd.exe": No error at
in thread Can't spawn "cmd.exe": No error at

This "advice" is wrong. Windows CMD does support 2>&1 and has since at least NT3.51 if not before.


Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Can't spawn "cmd.exe": No error at
by mgibian (Acolyte) on Jul 18, 2003 at 00:40 UTC
    One final bit... I have a file handle open for a file trace.log. Is there any way to append the output from the system operation to that file? Well, other than the obvious of closing the trace file, performing the system operation, then re-opening the trace file.

      No way that I know of, but closing the file and then re-opening for append either side of the system calls doesn't seem so onerous? Just make sure that you use the append form of redirection on your system commands and when re-opening the file in the calling program

      #! perl -slw use strict; open F, '>junk.log' or die $!; print F 'From calling program via F'; close F; system( 'perl -le"print q[This goes via STDOUT]; print STDERR q[This g +oes via STDERR];" 1>>junk.log 2>&1' ); open F, '>>junk.log' or die $!; print F 'From calling program via F'; close F; __END__ P:\test>type junk.log From calling program via F This goes via STDERR This goes via STDOUT From calling program via F

      Examine what is said, not who speaks.
      "Efficiency is intelligent laziness." -David Dunham
      "When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller