I will work on a patch to use libssh instead of starting a separate
ssh process. This might also be able to eliminate a socket in the "-via"
case, but I'll see. :)
I only have a Unix environment - is the "via"
mode supported on Windows or other builds?
-Eric
On Mon, 17 Jan 2011
14:23:41 -
Catching the failure to bind would certainly help (and should
probably be done no matter how the overall issue is addressed), but the
result of fixing just that part of the thread would be that the second
viewer either aborts due to the error (leaving the user to run the exact
same command again
Sounds like the real fix is to pay attention to the failure to bind with the
local port. I know that it displays a warning message. I do not know if it
returns an error code that is easy to capture. Instead of using an external
SSH, a solution could be to use the libssh library like is used by the
Developers,
I have encountered a bug in the way vncviewer manages
local ports when doing SSH tunneling (i.e. the "-via" option).
The
current logic finds a free TCP port by attempting a bind to a series of
predetermined port numbers (in network::findFreeTcpPort). If a bind
succeeds, the viewer
