Hi,
What I found, that even in Putty/PLink I see the same approach: when I start a command it continues after cancelling the command itself (press ctrl+c in command prompt) by default.
However when I forced plink to allocate a pty, (-t) it was working fine, and commands could be cancelled easily. So I assume, that the problem comes from PTY allocation.
Here I did not found any support for this on SshCommand level. A Shell/ShellStream can be used, or we should ask for PTY reservation feature for SshCommand. However this second option sounds much better. :)
(I found here only this about the topic: discussion:541597)
Thanks a lot for your help,
gyoreg
What I found, that even in Putty/PLink I see the same approach: when I start a command it continues after cancelling the command itself (press ctrl+c in command prompt) by default.
However when I forced plink to allocate a pty, (-t) it was working fine, and commands could be cancelled easily. So I assume, that the problem comes from PTY allocation.
Here I did not found any support for this on SshCommand level. A Shell/ShellStream can be used, or we should ask for PTY reservation feature for SshCommand. However this second option sounds much better. :)
(I found here only this about the topic: discussion:541597)
Thanks a lot for your help,
gyoreg