The problem reproduces on Mac OS X 10.4, 10.5, 10.6 : PPC/i386 : Server/Workstation. The problem does not reproduce on AIX, HPUX, SOLARIS, Linux. The hang occurs if the remotely executed script takes 20 or so seconds to return. The hang does not occur with instantaneous output shell commands like "uname -s" for instance. It does not matter whether remote script produces the output or not for hang to occur. The script actually finishes OK and does not get interrupted by this hang. So, the issue is only that the output is not displayed and the session hangs indefinitely without disconnecting. This forces user to press CTRL-C in the console application to return back to the command prompt. The problem originally also reproduced when using SharpSSH-1.1.1.13, so this is likely a legacy problem from the original version prior to project's fork. When tested similar functionality with Plink tool (see Putty download page) the problem did not reproduce. However, Plink.exe utility has an option to enable PTY allocation (switch -t: enablePtyAllocation). This played an important role on whether the hang reproduced on various OS or not with Plink. Proposed fixes: Option 1: Implement timeout mechanism in SshExec, this is more of a patch approach. Not serious permanent solution. Option 2: Fix the actual problem with the session hang by implementing PTY allocation.
