kavika13/RemCom — Issue #14: Remote command stdout and stderr can't be properly processed
Author: andrese
Created: 2012-02-10 15:26:09+00:00
State: open

Remcom client writes its own output mainly to stdout and remote command stdout and stderr is written too to remcom client stdout.

The result is that remote command stdout and stderr cant be properly processed.

Also remcom client return code is hidden by remote application return code so you can't process the client error codes.

I propose the following changes:

The client return code is now the real return code, and its even more detailed than before with the following error codes:

//Return Codes:

// (-1) Incorrect parameters
// (-2) Malformed credentials
// (-3) Invalid target name
// (-4) Bad credentials
// (-5) Could not connect to target
// (-6) Error copying executable
// (-7) Error copying service
// (-8) Error executing service
// (-9) Error connecting to remote service

Remote command return code is show at the stdout with the text: "Remote command returned XXX"

Now most of remcom client output goes to stderr.

Remote command stdout and stderr go to the cleitn stdout, but stderr is enclosed by the texts: "Remote program Stderr start:\n" and "Remote program Stderr end."