Please submit all bug reports to me no later than Wednesday 5/15 (or
remind me if I haven't fixed something yet.)
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to gra
I replied to you off-list already, but just to let the list know, there
is now a new parameter in the evolving version of the Java TurboVNC
Viewer (in SVN trunk) that allows you to disallow making any new
connections from the same viewer instance. This has the effect of
exiting the viewer when
Thanks, that will be useful.
On Fri, May 10, 2013 at 2:48 PM, DRC wrote:
> I replied to you off-list already, but just to let the list know, there
> is now a new parameter in the evolving version of the Java TurboVNC
> Viewer (in SVN trunk) that allows you to disallow making any new
> connection
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
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
I would find that helpful. Currently I'm forced to scan the log file to
determine success of the connection on the server side. Maybe you could
keep the asynchronous behavior default and just add a -sync option to
request a synchronous connect instead? Either way.
On Fri, May 10, 2013 at 4:05 PM,
