Greetings. We have been running VNC for about 10 years. Our platform is Sparc-Solaris. We recently moved an application that requires VNC to a new server, so I installed vnc-4_1_3-sparc_solaris. (The old server was an Ultra60 running Solaris 8; the "new" server is a V240 running Solaris 8 ;-)
It seemed to work, but we seem to have a behavior that is different than prior versions. I have an application running on host X. On host Y, I run the proprietary X-windows based monitor GUI. I snoop the conversation between X and Y to populate my status database. So to do this, I run the GUI with DISPLAY=host:1 via VCS High Availability software (i.e., in the background). Well, it *seems* that with vnc-4_1_3, VNC pops up an outline of the new window...and waits for a user to click on the screen where the window belongs. It waits forever.... or, until another window is coming in, then it seems to allow the first while waiting for confirmation on the second. I *think* that VNC used to not actually block I/O by the application. (note, I don't understand how it can, but I know what I saw :-) Connecting with VNCviewer and clicking resolves it. The current behavior makes VNC not work for our application. (I can build a workaround with testing, but would prefer to fix it :-) Any suggestions are appreciated. Thanks Seth _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
