As currently implemented, vncconnect stores the connection info in an X atom, and Xvnc reads this property asynchronously and establishes the connection. The connection attempt may or may not have been made by the time vncconnect exits, and thus, only Xvnc has any way of knowing whether or not the connection has failed.
However, it would be straightforward enough for us to adopt the same system used by TigerVNC/RealVNC. Their system uses a VNC X11 extension with a method called XvncExtConnect() that can be used to synchronously connect or disconnect a specific client, and it returns an error if the connection fails. We already have the VNC X11 extension, but currently only the clipboard functions are implemented in it, so it would be a simple matter of adding the connection functions and modifying vncconnect to use them. On 5/10/13 2:40 PM, Kevin Van Workum wrote: > I noticed that vncconnect's exit status is true if it can connect to the > vncserver even though the connection to the viewer could not made. The > server knows that the connection to the viewer was not established as > evidenced by the "connection failed: Connection refused" message in its > log file. Is there any way to include this information in vncconnect's > return status? Maybe a different return status for vncconnect? Or just > print something to stderr? ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
