1
Vote

Client does not capture stdout and stderr

description

The client component does not actually capture the standard out and standard error of processes it spawns.
 
There is an option for the client to do so in the messaging, but I never put the code in place.
 
I envision the client reading the stdout and stderr streams to text files off the same name as the process it executes. For instance, if I executed notepad.exe, the stdout and stderr would be notepad.exe.out and notepad.exe.err (I'd add numbers to make sure we don't overwrite files). These files would then be returned to the server using the same return resources mechanism. The server would name the files [LogFilename].[command].[out|err]. Again, in the case of multiple commands running, the commands would increment with numbers.
 
An alternative to reading the .NET streams is to append the redirector '>' argument to the command.

comments

joes wrote May 9, 2008 at 8:00 PM

Because the alternate redirector is available for commands, I will re-prioritize this to 1.00. It may even get dropped for v2.

wrote May 9, 2008 at 8:00 PM

wrote Feb 1, 2013 at 3:35 AM