I had the same problem in similar testing I have done.  OpenSSH does not return an error code for port bind failures.  If someone knows of a way to do this without opening ssh in a pipe and parsing the output, I would like to hear it too....  This was my main reason in suggesting something like libssh.  Using it guaranteed getting the detailed error status and being able to act on it by requesting another port etc.




On 02/14/2011 05:02 PM, Eric Stadtherr wrote:

Do you know of a way to check for the successful bind? One of the behaviors that drove me down the libssh path was that /usr/bin/ssh happily continues running despite failing to bind to the local port. Therefore there is no exit status to interrogate for success/failure. Can you think of a different way to check for successful bind?

--
Robert Goley

FOSS Implementation Specialist
Toll Free: (800) 338-4984
Local: (770) 479-7933
Fax: (770) 479-4076
www.openrda.com

America's only Free & Open Source fund accounting software company.
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Reply via email to