SSH Serial Connection Hangup (wodSSH / wodSSH.NET)
The microcom command itself will create a lock file and can hold the connection waiting for a response. It will lock a Putty session with the same command, only executing ctrl+X and ctrl+C can break out of it. Unfortunately, these commands are not captured in the same way here.
I am trying to create an asynchronous terminal session, similar to Putty, so that the user can enter and receive response freely. Initially i need to automatically execute the create session command. If I set the timeout to 30 seconds to the connection, it will prevent the locked response, however this will be applied to the user's interaction and he will receive the "timeout expired" error if there is a delay in activity.
Is there a way to apply a timeout for an individual command/response, instead of having it globally applied to all commands in a connection?
Complete thread:
- SSH Serial Connection Hangup - Mike D, 2014-11-19, 03:08
![[*]](themes/default/images/complete_thread.png "Open whole thread")
- SSH Serial Connection Hangup - Jasmine, 2014-11-19, 07:21
- SSH Serial Connection Hangup - Mike D, 2014-11-20, 06:03
- SSH Serial Connection Hangup - Jasmine, 2014-11-20, 15:42
- SSH Serial Connection Hangup - Mike D, 2014-12-04, 04:09
- SSH Serial Connection Hangup - Jasmine, 2014-12-04, 09:42
- SSH Serial Connection Hangup - Mike D, 2014-12-04, 04:09
- SSH Serial Connection Hangup - Jasmine, 2014-11-20, 15:42
- SSH Serial Connection Hangup - Mike D, 2014-11-20, 06:03
- SSH Serial Connection Hangup - Jasmine, 2014-11-19, 07:21
