My case: I have a command that runs on the remote system that creates a large amount of output very fast (either on STDOUT or STDERR, does not matter which) It seems there's a limit reached (value unknown) that, if this limit is hit and you 'switch' to check the other data channel, it causes locking in the module. That is, the large amount of data is on STDOUT. I read a bit of it, but bounce to make sure STDERR is not filling up, I can no longer read from STDOUT. Attempts to do so return 0 bytes, causing a "lockup" case that I cannot recover from. Anyone know how to avoid/correct this?