2 Commits (8fb8b2cffc54e4e724dffb1afb45219152c49fda)

Author	SHA1	Message	Date
James Bardin	2d7dc605a0	get communicator errors from a remote.Cmd ... The remote.Cmd struct could not convey any transport related error to the caller, meaning that interrupted commands would show that they succeeded. Change Cmd.SetExited to accept an exit status, as well as an error to store for the caller. Make the status and error fields internal, require serialized access through the getter methods. Users of remote.Cmd should not check both Cmd.Err() and Cmd.ExitStatus() until after Wait returns. Require communicators to call Cmd.Init before executing the command. This will indicate incorrect usage of the remote.Cmd by causing a panic in SetExitStatus.	8 years ago
Sander van Harmelen	c9e9e374bb	Adding some abstractions for the communicators ... This is needed as preperation for adding WinRM support. There is still one error in the tests which needs another look, but other than that it seems like were now ready to start working on the WinRM part…	11 years ago