client output not available in server log

[Javier Collado]

When the client fails to execute correctly, the output isn't available in the server logs:

INFO: Running command through SSH: utah -r /tmp/master.run -o /var/log/utah/utah-4-quantal-amd64_master.run_tmp
DEBUG: Closing SSH connection
WARNING: Return code: 255
DEBUG: Standard output follows:
DEBUG: Standard error follows:
ERROR: utah failed with return code: 255

This makes difficult to troubleshoot a problem in the client. The reason for the output to be missing is that the `-o <file>` argument is used to redirect the output that is usually printed to stdout to a file.

To make log more complete, the `-o <file>` option shouldn't be used. Instead, the results printed to stdout should be captured and stored in a file later. This way we get the results in a file on a successful execution or the output with the error messages in the log file.