SSH Timeout Feature Leaves Behind Processes on Target Host about train

[Vasu1105]

@clintoncwolfe Currently looking at the code what I understood is its actually timing out the session and closing it instead of actually timing out the command execution which we want to do if I am not wrong. That is we should timeout the sleep 60 but we are timeout the session. The command which I tried is behaving properly is timeout 2s sleep 60 which we really need to execute but what we currently executing the sleep 60 and somewhere as per my understanding closing actual connection or session https://github.com/inspec/train/blob/master/lib/train/transports/ssh_connection.rb#L360

[james-stocks]

That idea from @Vasu1105 is one I also considered - prefix the command string with timeout
I was wary about that option because it assumes timeout is on path on the target. Maybe it would be acceptable (but a little slower) for train to send which timeout to test if the target will support this?

Rolling back the entire command timeout feature

It would be nice to keep the feature for winrm , if that connection type is working OK.