Hi all,
This is actually a 2-in-1 patch (not sure if that is a good idea). I ran
into 2 problems with the old version:
1) When a VNC desktop is running, most users (accidentally) log out once
or twice, and then complain that their screen is black (or worse, has a
ghost image of the desktop).
Hi,
On 03/01/2011 12:13 PM, DRC wrote:
TurboVNC implements this more simply as a vncserver -fg switch, which
means run in the foreground. It does the same thing you are doing
below, except that it uses the built-in kill() function, which is safer
than trying to invoke another instance of
Good work digging into this problem. I am glad to hear this is only
a Windows problem. It confirms my limited testing of this issue on
other platforms. Do you have any preferences of the two solutions?
Robert
On 02/26/2011 12:42 PM, Martin Koegler
On 3/1/11 7:03 AM, Sebastiaan Breedveld wrote:
As far as checking for the VNC password, we're no longer requiring
VeNCrypt to be specified in the -SecurityTypes parameter, so checking
for that won't work. The correct approach is to check whether
-SecurityTypes is not specified -- or --
